rippled adds TransactionProposalCancel, the third transaction of the on-chain Cosigner feature

Victoria Shinder07 October 2026, 07:331 min read

The rippled repository merged pull request #7979, "Add TransactionProposalCancel for Cosign", on 6 October. It adds TransactionProposalCancel, transaction type 94 in the Cosigner specification §7, which deletes a TransactionProposal ledger entry and releases the proposer's reserve.

Where it fits. It is the third transaction of the On-Chain Cosigner feature described in XLS-0103, building on TransactionProposalCreate (#7887). It is gated behind a new amendment, featureCosign.

Who may cancel.

• While a proposal is live, only its owner (the proposer) or its target (the proposed transaction's Account, or the Delegate named in it) may cancel it; anyone else gets tecNO_PERMISSION.
• Once it is terminal, because its Expiration has passed or the ledger sequence is strictly past the proposed transaction's LastLedgerSequence, anyone may delete it. The PR says this mirrors the ordinary transactor's tefMAX_LEDGER rule.

Errors and restrictions. A zero ProposalID returns temMALFORMED, a missing entry tecNO_ENTRY. Proposals can no longer propose a Cancel, nor hide a proposal transaction inside a proposed Batch (XLS-0103 §5.3.1).

Tests. The change includes a shared test helper and a 19-case suite covering authorisation, terminal boundaries, and interactions with Batch, multisigning, sponsorship, tickets and nesting.