Transaction pinning is when an attacker exploits limits in mempool relay policy to stop an incentive-compatible transaction from being accepted or fee-bumped. BIP 431's TRUC rules (also called version 3 transaction relay) were designed to make pinning harder for contract protocols such as Lightning, where parties sign time-sensitive transactions to broadcast later.
Sources and checks
T1BIP 431, Topology Restrictions for PinningBIP, says this directly
malicious actors may sometimes exploit limitations to prevent incentive-compatible transactions
Motivation, read 2026-11-20
T1BIP 431, Topology Restrictions for PinningBIP, says this directly
Pinning is consequential to contracting protocols in which untrusted parties construct and sign time-sensitive transactions to be broadcast on-chain later
Motivation, contracting protocols, read 2026-11-20
T2Bitcoin Optech topic, Version 3 transaction relayBitcoin Optech, supports part of it
Combined with package relay, these policies help enable the use of dynamic feerates with LN onchain transactions.
Topic summary, read 2026-11-20
T2Bitcoin Optech topic, Version 3 transaction relayBitcoin Optech, says this directly
designed to prevent pinning attacks.
Topic summary, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 4/4
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 17:28 UTCblock 976,759
Published Revision 1, run 2026-11-20-seed-fees-and-mempool