Wallet sources
Import a protected source, then create named wallets and exact-network addresses.
Step by step
- From Overview, choose Add wallet or address, then Import a recovery phrase. Give the source a name, choose its visibility and select exact networks already enabled by the organization. Creating this record alone imports no keys.
- Open the source and choose Generate in protected storage or Import in protected window. Complete platform confirmation, then choose Open protected input. Enter the phrase and optional BIP39 passphrase only in that separate window. The passphrase may be empty; case and spaces are significant.
- Wait for the public result to be accepted. A prepared request, missing response or unknown result does not mean the source is ready. Read or recover the same request instead of creating another source to retry.
- After admission, create a named wallet under the source. Declare the actual economic owner, then complete its public child-source admission. Ownership metadata creates no funds or credit.
- Choose an enabled exact network and reserve an address. Complete the original allocation; a reservation is not yet a receiving address. Only a materialized address can be copied or opened in Receive.
- An unfinished allocation retains its original operation ID and public terms on this device, scoped to the actual organization and account. Continue the saved operation explicitly after reloading; no work replays automatically.
- A ready address shows its saved Wallet branch and full derivation path. The exact network remains separate: matching paths do not mean matching chains or spending authority.
- After Source connected and Wallet connected, add an address on the required network. On a ready address, Receive is the main action for copying the address or showing its QR code. Add address signer remains a separate setup action when permitted; connecting a source does not establish a balance or permission to send.
- At a ready address, choose Add address signer. Select a paired Sign Node and review the address, exact network and path. The original service uses its saved public source ID; for another signer, enter only the public source UUID from that signer’s import receipt. It must already hold the matching source; CRM does not copy keys.
- Create the verification request, then open its details under Address signers for this source. Choose Verify address on Sign Node, inspect the public evidence and fingerprints, select the review checkbox and confirm the association before expiry. A proof alone is not an active association.
- After an interrupted request, read the same stored ID. If the invitation has not reached the backend, Resume original request sends only its saved public terms and original ID. Recover original proof retrieves the existing proof; it never changes the address, signer or source.
- Association revocation requires typed DELETE and platform confirmation. It retains evidence and keys. Confirmed is a saved state, not online status or automatic spending permission. A changed service registration needs renewed review. Finish association review clears only the local invitation journal after confirmation, revocation or expiry.
- The original creator can continue proof and confirmation after signing in on another device. These actions use the backend’s creator flag, current rights and stored state; a local journal does not grant authority.
- To send from an admitted Node address, choose the asset, recipient and amount, then estimate the fee. Review the exact terms and prepare the original transfer. A quote reserves nothing; preparation does not send funds.
- Transfer details show each rule’s required quorum and actual approved, rejected and still-needed counts, with the time checked. The current user’s saved decision is shown separately. Rules changed or Voting closed prevents a new vote; the initiator cannot approve their own transfer. Approve and Reject appear only when current backend eligibility and permissions allow them. These counts do not authorize signing.
- The original initiator selects an active signer for this exact address, reviews its fingerprints and confirms signing and sending. The backend rechecks current access, rules, approvals and the hold. The signer selection is saved before the request is sent.
- After a lost reply, unfinished task or earlier approval rejection, choose Continue original signing and sending. Confirm the same operation and signer. The backend resumes an existing task; if dispatch never started, it may sign the original transfer for the first time after rechecking. No alternate signer or replacement transfer is substituted.
- Recover original signed result is a separate action: it only retrieves and saves the original result, without a fresh signature or sending. For an already signed transfer, relay and reconciliation are separate permission-controlled actions. None runs automatically when opening or reloading the page.