An onchain cosigner draft joins the XRPL standards repository
Serguey Asael Shinder2 min readThe XRP Ledger standards repository took in a draft for an Onchain Cosigner on 16 September 2026. Pull request #613 was authored by shawnxie999 with ckeshava and merged by mvadari, adding 1,203 lines in a single file after 31 commits and 126 comments on the thread.
This is a discussion of a document rather than a report of a launch, and the date is six days old — the XRP desk's feeds carried nothing newer, so this is the project's own repository rather than coverage of it.
Two details in the merge history say what the draft is for. It grew out of an earlier "Cosign draft" (#586), and a separate change describes designing a transaction_proposal RPC around per-account signing status. That phrase is the substance: the proposal is concerned with a transaction that exists, is incomplete, and needs to be tracked while signatures accumulate against the accounts expected to provide them.
What it means
Multi-party signing on the XRP Ledger already exists — SignerLists and multisigned transactions are long-standing. What has never been standardised is the part around it: where a partially-signed transaction lives while it waits, how a participant discovers that their signature is the one outstanding, and how any of that is queried without a private arrangement between the wallets involved.
Today that coordination happens off-ledger, in a vendor's infrastructure or a shared document, which is exactly where multisig custody arrangements tend to fail — not in the cryptography but in the bookkeeping of who has signed and what they signed. An RPC organised around per-account signing status is an attempt to make that queryable rather than arranged.
⚠️ Read the status precisely. A draft merged into the standards repository is a numbered document open for review; it is not an amendment, it has no validator vote behind it, and nothing in rippled implements it because it was merged. The thing to watch next is whether it acquires an XLS status change and a reference implementation — and we have not reviewed the specification's contents here, only its arrival.