On the official site of Giga (Brice Patterson / @gigatronaura), this note covers XRPL.
The Current Atmosphere Around XRPL Updates
Crypto participants checking developer channels on a Tuesday evening in late August see fresh activity in the XRPL Standards repository. The latest entry sits alongside existing proposals without overlapping prior tagged releases. Market participants watching XRP at 1.45 dollars note the separate timing of this technical discussion from recent price movement.
Draft Creation and Timeline
RippleX engineers created the On-Chain Cosigner draft on July 14, 2026. The formal GitHub discussion under XRPL-Standards #589 began on July 23. The proposal introduces a TransactionProposal ledger object that holds an unsigned transaction. Signers add their signatures directly into the transaction's Signers field on ledger. Anyone can then copy and submit the completed transaction.
Transaction Types and Requirements
Three new transaction types appear in the draft: TransactionProposalCreate, TransactionProposalSign, and TransactionProposalCancel. An RPC endpoint called transaction_proposal supports these actions. The draft requires XLS-49 as a prerequisite. Reserve costs stand at five owner-reserve increments for a standard proposal, which equals one XRP at current settings, and ten increments for a Batch proposal, which equals two XRP.
Clear Separation from Existing Releases
The draft carries no enabled status. It does not appear in xrpld 3.3.0 or xrpld 3.2.0. The proposal stays distinct from BatchV1_1 XLS-56, the xrpld 3.2.0 rename effort, XLS-65, XLS-66, and XLS-96. Latest tagged server release remains xrpld 3.3.0, so operators running current versions encounter no change from this draft.
Reader Actions to Consider
Open the GitHub discussion at XRPL-Standards #589 to review the full proposal text. Compare the described flow against current multi-sign setups already running on mainnet. Track future comments in the thread for any movement toward formal numbering or implementation discussion. Test environments can be prepared once a tentative XLS number receives confirmation. Monitor the XRPLF rippled releases page for any future integration notes.
Technical Flow in Simple Terms
A proposer first creates the TransactionProposal object. Additional signers append approvals through the dedicated sign transaction. Cancellation remains available through the third type if needed. The design keeps the unsigned transaction visible on ledger until submission occurs. This structure differs from off-chain collection methods in use today.
Why the Distinctions Matter
Developers and node operators benefit from knowing this draft does not alter existing BatchV1_1 or 3.2.0 paths. Running the latest tagged release keeps the network unchanged. The reserve increments provide a clear cost signal for anyone planning to experiment once the amendment advances.
Checking Progress Going Forward
Visit the XRPL-Standards repository regularly for updates to discussion #589. Compare any new comments against the confirmed facts of creation date and transaction types. This keeps observers aligned with the actual status rather than assumptions about future releases.