XRPL's Cosign amendment lands in rippled: multisig proposals go on-ledger
Serguey Asael Shinder1 min readThe rippled repository merged pull request #8205 on 28 September, introducing the first version of a Cosign amendment for the XRP Ledger. It implements the specification proposed in XRPL-Standards pull request #613.
Today an XRPL multi-signature is assembled off the ledger: signers pass a transaction around, collect enough signatures and submit the result. The Cosign amendment moves that coordination onto the ledger. This pull request delivers the first step of the lifecycle: a new ledger object, TransactionProposal, which stores an unsigned proposed transaction while signatures are collected, and a new transaction, TransactionProposalCreate (type 93), which posts such a proposal with the proposed transaction and an expiration. Proposals are returned by account_objects and can be looked up through ledger_entry.
The rest of the lifecycle is still to come. According to the pull request, follow-up changes will add TransactionProposalSign, Execute and Cancel, which are the steps that let signers attach signatures and have the transaction run. The amendment is marked as not supported and set to vote "no" by default, so it is not enabled on any network and validators cannot yet vote for it.
Why it matters
For institutions and treasuries that hold XRP under multi-signature control, the hard part is usually coordination, not cryptography: who has signed, which version they signed, and when the request lapses. Putting the proposal on the ledger gives every signer the same view of that state. What has landed is the storage and the create step; whether the feature works as a whole will only be clear once the signing and execution changes arrive.