Groups & capacity

Import your approved groups

In Settlements, open Choose from approved groups and import your independently obtained directory. It contains 1–8 pinned policies, unique group IDs and an explicit depositsEnabled preference. Every entry shares the same network, token and denomination. The browser workspace accepts testnet FT groups.

The file is validated locally and stays in memory. It contains no API origins, private notes or passwords. Enter each group’s HTTPS Settlement API separately; localhost HTTP is supported for local use. Importing the directory makes no network requests.

Check capacity before selecting

Each group has 256 total tree outputs, including private-transfer outputs. Withdrawals do not restore capacity. The capacity endpoint checks the registry and at most the first member; a partial scan with no observed eligible vault is not proof that every vault is unavailable. Use the CLI for complete verified member discovery.

This snapshot reserves no output slot and does not establish wall-clock freshness of the RPC chain head. A failed refresh or edited API address invalidates the previous result. Payment review still performs fresh preflight and liquidity checks.

1. Enter the Settlement API for a group and choose Check. The API policy must match every independently approved pin.
2. Review the reported block, remaining output slots and whether the first verified member can accept a deposit.
3. Choose Use for deposits for an enabled group with observed capacity. Selection checks the API again.
4. Download the selected policy for local CLI preparation, connect your wallet and unlock that group’s encrypted journal.

Keep the original group for recovery

Full or deposit-disabled groups remain selectable with Use for recovery. The workspace verifies that group’s API and opens its own journal namespace. New deposit imports are blocked in recovery mode, while existing journal operations retain their retry/refund paths.

Choose the group in which the original note was created. Imported public plans must match that policy. A different available group cannot replace an existing note’s domain, payout vault or signed invoice policy. Lock the journal before changing groups.

If funds have not been sent and the original group fills, generate a fresh note for another approved group. Keep every funded note and its original trusted policy for withdrawal. Group changes do not migrate notes or merge privacy sets.

Prepare notes and plans locally

Set CORE_NOTE_PASSWORD securely as described in the Core guide; never pass it as a command argument or upload a private note to the API. The Private notes page opens compatible browser backups locally. group-note follows the directory order or an explicit group preference. Existing notes remain group-bound.

Protocol fees remain 0.15% added on top of principal for each deposit and withdrawal. Token registration, NEAR storage and gas remain separate. Contracts and groups must already be deployed and independently approved.

npm run cli -- groups-status approved-groups.json https://rpc.testnet.near.org
npm run cli -- group-note approved-groups.json https://rpc.testnet.near.org receiver-note.encrypted.json
npm run cli -- group-deposit-args approved-groups.json https://rpc.testnet.near.org receiver-note.encrypted.json FRESH_DISCLOSURE_ROOT
npm run cli -- group-spend-args approved-groups.json https://rpc.testnet.near.org original-note.encrypted.json withdraw-action.json public-withdrawal.json

Invoices remain group-bound

Checkout verifies the policy in the merchant’s signed invoice and does not expose group switching. If a merchant needs a new group for new payments, they must issue a new signed invoice for that independently trusted policy. Existing funded notes can still pay an invoice matching their original group.