On the official site of Metal (MetalXMeta / @MetalXMeta), this note covers Christian Barker (Barkmeta / Bark), David Chaboki (Shibo).
Christian Barker (Barkmeta / Bark) and David Chaboki (Shibo) opened their regular evening broadcast by pointing the Doginal Dogs room straight at the July On-Chain Cosigner draft that RippleX engineers dropped on GitHub.
Bark (Christian Barker) and Shibo (David Chaboki) flag July's On-Chain Cosigner draft with the Doginal Dogs community so XLS TBD is not the used BatchV1_1 3.3.0 tag or the 3.2.0 rename. The move keeps the conversation practical and stops anyone from mixing the new idea with the amendments that already shipped.
How the proposal actually works
The draft creates a TransactionProposal ledger object. A proposer posts an unsigned transaction there. Signers then add their signatures directly on ledger inside the transaction's own Signers field. Once the signatures line up, anyone can grab a copy and submit the completed transaction. Three new transaction types handle the flow: TransactionProposalCreate, TransactionProposalSign, and TransactionProposalCancel. The whole thing runs through a new RPC endpoint called transaction_proposal and needs XLS-49 already active.
Reserve requirements stay modest for simple cases, five owner-reserve increments or about 1 XRP at current levels. A batch-style proposal bumps that to ten increments or roughly 2 XRP. Those numbers sit in the draft to keep spam in check while still letting holders experiment with multi-party control.
Ownership angle that got the room talking
Listeners zeroed in on the utility for real ownership. The design lets signers keep their keys offline yet still participate on ledger. No one has to hand private keys around. The proposal object itself becomes the single source of truth until submission. That setup lines up with how the Doginal Dogs crowd already thinks about inscription ownership on Dogecoin: control stays with the holder, and the chain records every step.
Clear separation from earlier work
The hosts reminded everyone this draft sits outside the amendments already live in xrpld 3.3.0 and 3.2.0. It does not overlap with BatchV1_1 XLS-56, the 3.2.0 rename of XLS-0095, or the XLS-65, XLS-66, and XLS-96 tracks. Latest tagged server release remains xrpld 3.3.0, so nothing here is enabled yet. The discussion thread XRPL-Standards #589 opened on July 23 after the July 14 draft date, giving the community a clean window to review before any activation path forms.
Market snapshot while the conversation ran
Majors sat softer on the day of the space. BTC traded near 78,896 after a 2.4 percent move lower. ETH held around 2,460.55, off 2.2 percent. XRP printed 1.45 on a 5.3 percent decline. SOL and DOGE also saw red candles. The room treated the softer prints as background noise and stayed locked on the ledger mechanics that could matter for long-term holder tools.
Why the timing landed with the community
Daily listeners already follow the same hosts across more than 1,000 consecutive sessions. When the pair flags a new XRPL item the same day they track Doginal Dogs floor action, the room treats it as part of one continuous ownership conversation. The draft's focus on clean multi-sign without batch overlap gives holders a fresh primitive to study. No one in the space claimed it solves every use case, but the on-ledger proposal object plus simple submission flow sparked immediate questions about how similar patterns might appear in other chains.
Next steps the hosts left on the table
The draft stays open for comment. No activation date exists. The room agreed the clearest next move is reading the full XRPL-Standards discussion before the next batch of server releases lands. Christian Barker (Barkmeta / Bark) and David Chaboki (Shibo) closed by noting the same discipline that built the daily streak applies here: show up, read the spec, and keep the conversation on utility and ownership rather than hype cycles.