Topologically Restricted Until Confirmation (TRUC)

Definition: Topologically Restricted Until Confirmation (TRUC) is an opt-in Bitcoin transaction-relay and mempool policy for transactions with version number 3. Nodes implementing the policy limit how unconfirmed TRUC transactions can depend on one another, with the goal of making replacement and fee-bumping behavior more predictable and harder to pin. Bitcoin Core treats version-3 transactions as TRUC-standard since v28.0, but this is node policy—not a consensus rule that changes which blocks are valid.12

Proposal Read BIP 431 · Status: Draft
Bitcoin Core Version-3 transactions are standard under TRUC policy as of v28.0.
Rule type Local relay and mempool policy; not a Bitcoin consensus change.
Directories Bitcoin Technology & Infrastructure

What TRUC changes

Bitcoin transactions carry a version field. Under TRUC, a wallet opts a transaction into a stricter policy by setting that field to 3. A node that implements the policy applies additional standardness rules to the transaction’s unconfirmed ancestors and descendants. In broad terms, an unconfirmed TRUC transaction can have at most one unconfirmed ancestor and one unconfirmed descendant. The proposal also caps a TRUC transaction at 10,000 virtual bytes (vB); a TRUC transaction with an unconfirmed TRUC parent is limited to 1,000 vB. These are policy constraints on transactions waiting in a node’s mempool, not new validity rules for confirmed blocks.1

The topology limits place a bound on how many related unconfirmed transactions a node must consider when deciding whether to accept or replace one. BIP 431 also treats a TRUC transaction as replaceable under its policy, even if it does not signal BIP 125 replaceability in the usual way. Bitcoin Core’s stated rationale is to make replacement decisions more incentive-compatible and fee-bumping more robust by restricting the shapes of transaction chains that can be used to pin a presigned transaction.12

Why topology matters for fee bumps

With Child Pays for Parent (CPFP), a child transaction pays enough fee to improve the combined fee rate of itself and its unconfirmed parent. In protocols that sign a transaction before the fee market is known—such as Lightning channel commitments—another party may try to make the parent difficult to replace or to attach a fee-paying child. This is called transaction pinning. Restricting unconfirmed descendants and limiting their size reduces some avenues for that interference and makes package fee calculations easier for participating nodes.

TRUC is designed to work with package evaluation and relay policies, including one-parent-one-child package fee bumps. It is not a fee market guarantee: a wallet still needs a way to construct and broadcast a suitable replacement or child, peers must accept it under their policies, and a miner must choose it for a block. The policy also narrows transaction construction. For example, a child spending from an unconfirmed TRUC parent must fit the smaller size limit and cannot add a second unconfirmed ancestor under the specified topology rules.2

Policy, consensus, and support

TRUC does not change Bitcoin’s consensus validation. A version-3 transaction is not valid merely because it follows TRUC, and a consensus-valid transaction does not become invalid on-chain simply because it violates a local mempool policy. Policy determines what a node relays or holds before confirmation; miners can also use their own transaction-selection policies. Bitcoin Core’s implementation index says version-3 transactions are treated as TRUC-standard from v28.0, while the BIP itself remains a draft. Wallet and service support can differ, so a user should not assume every route to the network handles v3 transactions identically.23

Bitcoin Core’s later mempool changes also matter when reading older descriptions. Version 31.0 removed the older CPFP carve-out and release notes point smart-contracting use cases toward TRUC transactions and sibling eviction for similar functionality. This is an evolving set of policy tools, not a one-time consensus activation. Applications should follow the release notes and test the exact node and wallet versions they use.4

History

  • January 10, 2024: BIP 431 was assigned as a draft proposal for topology restrictions intended to improve transaction replacement and reduce pinning risks.1
  • Bitcoin Core v28.0: Version-3 transactions became standard under opt-in TRUC policy across Bitcoin Core’s supported networks; this did not activate a consensus change.2
  • Bitcoin Core v31.0: The release removed the CPFP carve-out and documented TRUC and sibling eviction as a way for some applications to obtain similar behavior.4

Last updated: November 13, 2026.

Criticisms

  • TRUC is a mempool and relay policy, so behavior depends on the software and configuration of nodes, wallets, and miners involved.
  • The strict ancestor, descendant, and size limits constrain transaction design. Complex unconfirmed chains may need restructuring or may not fit the policy.
  • TRUC can reduce some pinning strategies but does not eliminate every fee-bumping, propagation, or miner-incentive risk.
  • Because the BIP remains Draft and policy evolves between Bitcoin Core releases, implementers should distinguish the BIP’s proposal text from the behavior of a particular software version.

Related Terms

Related Articles

See Also

Sources

  1. Zhao, Gloria. “BIP 431: Topology Restrictions for Pinning.” Bitcoin Improvement Proposals. Assigned January 10, 2024. Accessed November 13, 2026. https://github.com/bitcoin/bips/blob/master/bip-0431.mediawiki.
  2. Bitcoin Core. “Bitcoin Core 28.0 Release Notes.” Bitcoin Core. Accessed November 13, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-28.0.md.
  3. Bitcoin Core. “BIPs Implemented by Bitcoin Core.” Bitcoin Core Documentation. Accessed November 13, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/bips.md.
  4. Bitcoin Core. “Bitcoin Core 31.0 Release Notes.” Bitcoin Core. Accessed November 13, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-31.0.md.