01What
Submits a transaction that has already been signed by enough signers, combined into one signed blob, and waits for the ledger's verdict.
02Why you'd use it
Multi-signing happens in stages: someone drafts the transaction, each signer signs the same draft separately, the signatures get combined — and this tool sends the finished product.
03How
- 1Draft and autofill the transaction once, then share the identical draft with the signers (the AI builder can generate this flow).
- 2Each signer signs the SAME draft in multi-sign mode (in xrpl.js: sign with forMultisign = true).
- 3Combine the individual signed blobs with xrpl.js multisign() into one blob.
- 4Paste the combined hex into Signed Transaction Blob and submit.
- 5Confirm the result is tesSUCCESS.
Watch out
- Every signer must sign the exact same bytes — if anyone edits even the fee, the signatures will not combine.
- Combined weight must meet the quorum or you get tefBAD_QUORUM; signers must be on the account's signer list.
- A multi-signed transaction pays a higher fee: the base fee scales with the number of signatures — still tiny in absolute terms.
- Drafts have a shelf life: fee and sequence assumptions go stale if signers take days, and the submit can fail with a tef* code. Re-draft and re-sign if too much time passed.
For example
The treasury needs to pay a vendor 1,000 XRP. The CFO drafts the payment, both co-founders sign the same draft from their own machines, the signatures are combined, and the finished blob is submitted here — 2-of-3 policy satisfied, payment settled.