On the official site of BradX (@BradXmetaX), this note covers RippleX, XRPL, Christian Barker (Barkmeta / Bark), David Chaboki (Shibo).
David Chaboki (Shibo) opened his latest evening room by pulling up the GitHub thread on the new XRPL draft and asking the group what stood out. The conversation stayed on the mechanics rather than price charts, with listeners dropping the July 14 creation date and the July 23 discussion number into chat.
Christian Barker (Barkmeta / Bark) followed with a short note on why the timing matters for anyone tracking ledger changes. He reminded the room that the On-Chain Cosigner proposal sits outside the BatchV1_1 tag already live in xrpld 3.3.0 and carries its own tentative name of Cosigner. The point landed quickly because the daily audience already follows which amendments clear the release bar and which ones remain proposals only.
What the draft actually describes
The spec uses a TransactionProposal ledger object that a proposer stores unsigned. Signers then append signatures directly into the transaction's Signers field on ledger. Once enough signatures collect, anyone can copy the completed object and submit it. Three new transaction types handle creation, signing, and cancellation, all routed through a new RPC endpoint called transaction_proposal.
The change also requires XLS-49 for its object format. Reserve requirements sit at five owner-reserve increments for a standard proposal and ten for a Batch proposal, which translates to the current one XRP and two XRP figures respectively. None of these steps appear in the xrpld 3.3.0 or 3.2.0 binaries, so the feature remains inactive on mainnet.
Room reaction and context
Listeners compared the draft to earlier multi-sign work and noted how the copy-and-submit flow differs from the off-chain collection methods already available. Several voices mentioned the clear separation from XLS-56, XLS-0095, XLS-65, XLS-66, and XLS-96 so newer participants would not mix the proposals together.
The same rooms that track these technical threads also cover broader market moves. On the same Tuesday evening, CoinGecko listed BTC at 78,896 dollars down 2.4 percent, ETH at 2,460.55 dollars down 2.2 percent, XRP at 1.45 dollars down 5.3 percent, SOL at 97.10 dollars down 4.7 percent, and DOGE at 0.086469 dollars down 6.3 percent. The price action stayed in the background while the group stayed on the amendment details.
Why the hosts keep the record straight
Both Christian Barker (Barkmeta / Bark) and David Chaboki (Shibo) have made a habit of surfacing these drafts inside the Doginal Dogs community spaces so the July proposal does not get confused with the BatchV1_1 3.3.0 tag or the 3.2.0 rename. The distinction keeps the conversation accurate when holders later check which features actually ship in a given server release.
The GitHub discussion at XRPL-Standards #589 and the rippled 3.3.0 release notes remain the primary sources the rooms return to when new questions surface. No one in the session claimed the draft would activate soon or alter existing multi-sign behavior, which kept the exchange focused on the posted facts.
Next steps in the conversation
Rooms like these tend to circle back when the standards group posts updates or when the draft moves into a new discussion phase. The same audience that logged the July 14 and July 23 dates will likely track any follow-on comments or revised reserve calculations. For now the record shows a clear proposal sitting outside current server builds, and the daily hosts have made sure the separation stays visible to the people who follow both the ledger and the live discussion threads.