A new proposal submitted to the XRP Ledger Standards repository could fundamentally change how multi-signature transactions are handled on the network. The initiative, called On-Chain Cosigne
A new proposal submitted to the XRP Ledger Standards repository could fundamentally change how multi-signature transactions are handled on the network. The initiative, called On-Chain Cosigner, is part of the ripple:native Ledger Standards framework and was authored by Shawn Xie, Zhiyuan Wang, Chenna Keshava B S, and Mayukha Vadari, a software engineer at RippleX.
The Problem With the Current Design
Multi-signature on the XRP Ledger is a security feature where multiple parties must jointly authorize transactions from a single account, with a shared account able to require multiple signers to approve a transaction before it can be submitted. The mechanic is widely used for treasury management and custodial services, but its current implementation has a meaningful operational gap.
Under the existing system, signers coordinate off-chain, meaning a single coordinator is responsible for collecting individual signatures and combining them into one submission. XRPL community member Vet has noted that if the coordinator loses signatures or goes offline during that process, the entire transaction can fail. The proposal identifies that off-chain dependency as the core weakness it is designed to address.
The On-Chain Cosigner proposal aims to improve multi-signature transaction coordination by enabling signers to approve transactions directly on-chain. By moving the collection and combination of signatures onto the ledger itself, the new design removes the single point of failure that currently sits with an off-chain coordinator.
What It Means for Institutional Users
Multi-signature functionality on the XRP Ledger enables accounts to require multiple cryptographic signatures from different keys to authorize transactions, and this enterprise-grade feature serves crucial roles in organizational treasury management, personal security enhancement, and shared account control scenarios where no single party should have unilateral authorization. Supporters of the On-Chain Cosigner proposal argue the upgrade would directly strengthen those institutional workflows by making the signing process more resilient and predictable.
RippleX developer Mayukha Vadari has previously emphasized that the ledger's progress should be measured by long-term improvements like infrastructure, liquidity, and institutional readiness rather than just transaction volume. The On-Chain Cosigner proposal fits squarely within that philosophy, targeting a structural improvement rather than a headline feature.
The proposal has been formally submitted to the XRPL Standards repository and is now open for community review. No timeline for a vote or activation has been confirmed.
Sources:XRP Academy: Multi-Signature Functionality on XRPLCoinpaper: RippleX Dev Explains XRPL Upgrades Beyond Transaction Volume