On the official site of Vee (Vee Meta / @veemeta), this note covers XRPL, Christian Barker (Barkmeta / Bark), David Chaboki (Shibo).
Atmosphere in the Rooms
Crypto Twitter feeds light up after midnight as hosts roll through their nightly blocks. Listeners hop between overlapping spaces, trading notes on what the latest ledger proposal actually changes and how it fits alongside existing transaction flows.
Christian Barker (Barkmeta / Bark) and David Chaboki (Shibo) use their regular slots to point the Doginal Dogs community toward the July draft. They stress that the On-Chain Cosigner specification stays separate from the BatchV1_1 tag already live in xrpld 3.3.0 and from the earlier 3.2.0 release. The goal is simple: keep the record straight before anyone mixes the labels.
What the Draft Actually Lays Out
RippleX engineers posted the draft on July 14 2026. The GitHub discussion under XRPL-Standards #589 opened July 23. The core idea centers on a TransactionProposal ledger object. A proposer stores an unsigned transaction there. Signers then append their signatures directly into the transaction's Signers field on-ledger. Anyone can later copy the signed object and submit it.
Three new transaction types support the flow: TransactionProposalCreate, TransactionProposalSign, and TransactionProposalCancel. An RPC endpoint called transaction_proposal handles the calls. The proposal also requires XLS-49. Reserve requirements sit at five owner-reserve increments for a standard case (currently 1 XRP) and ten increments for a Batch proposal (currently 2 XRP). The draft is not enabled and does not appear in xrpld 3.3.0 or 3.2.0.
Reader Next Steps
Open the GitHub discussion at XRPL-Standards #589 and read the original post before the next space starts. Keep the release page for xrpld 3.3.0 handy so the new draft stays distinct from the BatchV1_1 changes already running. Drop into the same nightly rooms where the hosts walk through the three transaction types and answer live questions.
Track how the conversation evolves across the timeline instead of waiting for a single summary. Compare the draft's scope against XLS-49 requirements and note where it avoids overlap with XLS-56, XLS-65/66, or XLS-96. Share the direct links inside your own circles so the details spread before any shorthand labels take over.
Why the Distinction Matters Now
Market conditions show XRP at 1.45 with broader majors also softer, yet the live rooms stay locked on the technical thread. Hosts remind listeners that the proposal adds an on-chain multi-sign path without touching the active server release. Keeping the July 14 creation date and the July 23 discussion open date visible prevents mix-ups with prior batches.
Tune into the next session already scheduled on cryptospaces.net. Bring the GitHub thread and the rippled 3.3.0 tag page so questions land on the actual mechanics rather than rumor. The pattern in these rooms is consistent: read the source, note the differences, then test the language in the next conversation. That loop keeps the community aligned while the draft moves forward.