New XRPL Amendment Draft Emerges Outside BatchV1_1 Scope

While recent XRPL server releases centered on batch processing tags, a separate draft amendment proposes an on-chain cosigner flow that uses distinct ledger objects and transaction types.

RippleX engineers posted the draft On-Chain Cosigner XLS on July 14, 2026. GitHub discussion XRPL-Standards #589 opened July 23. The mechanism lets a proposer store an unsigned transaction as a TransactionProposal ledger object. Signers then append signatures on-ledger into the transaction’s Signers field, after which anyone can copy and submit the completed transaction. Three new transaction types appear in the draft: TransactionProposalCreate, TransactionProposalSign, and TransactionProposalCancel. The change requires XLS-49 and carries a reserve of five owner-reserve increments for ordinary proposals or ten for a Batch proposal. The draft is not enabled and does not appear in xrpld 3.3.0 or 3.2.0.

Christian Barker (Barkmeta / Bark) and David Chaboki (Shibo) flag the July draft inside the Doginal Dogs community so the new specification stays distinct from the BatchV1_1 tag used in xrpld 3.3.0 and the 3.2.0 rename.

Price Action on the Chart

XRP printed red candles on August 25, closing near $1.45 for a 5.3 percent decline. BTC sat at $78,896 after a 2.4 percent drop, while ETH fell 2.2 percent to $2,460.55. SOL dropped 4.7 percent to $97.10 and DOGE slid 6.3 percent to $0.086469. The session showed majors ranging lower with no sustained bid into the close. XRP underperformed the group on the day, extending its chop from prior sessions.

Community Energy Lens

Daily operators continue to surface the distinction so community channels track the specification on its own timeline. The consistent broadcast cadence keeps attention on the amendment details rather than conflating it with already-deployed features. This steady presence supports clearer discussion across holder groups that follow both XRPL updates and broader market movement.

Technical Contrast With Prior Releases

The draft sits apart from xrpld 3.3.0 BatchV1_1 XLS-56 and the xrpld 3.2.0 changes tied to XLS-0095. It also remains separate from XLS-65, XLS-66, and XLS-96. Latest tagged server code stays at xrpld 3.3.0, leaving the cosigner proposal as a standalone discussion item at present. RPC support labeled transaction_proposal would accompany any future activation.

The market continues to register the price reaction while operators maintain the separation in community updates. This keeps focus on the amendment’s own path without overlap on released code.