Multisign Workspace

Coordinate a shared account#

Signatures are weighted approvals, not simply a count of wallets. Signing does not submit. The full shared-account transaction is shown before approval. Proposals and signatures stay in browser memory unless you explicitly export a JSON file; XRPFrontend does not store these proposals on its server. Exported signed files authorize the specified transaction and should be shared only with the intended coordinator.

1. 01

   Configure and verify the shared account signer list in Account Settings. Open Markets → Market Tools → Multisign Workspace, or use the link beside signer-list settings.

2. 02

   Prepare an XRP payment or import supported unsigned transaction JSON. Preparation obtains the current shared-account sequence, weighted signer list, network fee and ledger expiry. Export the proposal JSON.

3. 03

   Each signer imports the same proposal on the same network, reviews it and signs through Xaman. A compatible external tool can instead contribute an ordinary multisigned transaction blob. Export the updated proposal with collected signatures and send it to the intended coordinator.

4. 04

   Import updated proposal files or signed blobs to collect approvals. The workspace verifies signatures, exact transaction fields, signer membership and current key permissions. Submit only when the combined signer weight reaches quorum.

Expiry and changed account state#

Prepared proposals expire after 150 ledgers. Shared-account sequence changes, signer-list changes, disabled master keys or changed regular keys can invalidate approvals. The workspace rechecks these conditions before signing and submission. Expired or changed proposals must be prepared again and signed again. Fee and expiry cannot be changed after signatures are collected.

Direct signing uses Xaman; other compatible signing tools can import multisigned blobs. Temporary test wallets can sign on Testnet. Ordinary multisigning is separate from Batch participant signing. This workspace excludes Batch transactions, AccountDelete, tickets and delegation.

If submission reports a pending result, retain the hash and check ledger status before retrying. Do not create a new payment just because validation is taking longer.