Transaction Pinning

Overview

Transaction pinning makes a victim’s transaction difficult to replace, rebroadcast, or include by attaching or constructing related transactions that interact badly with node policy. The attacker exploits differences between consensus validity and mempool acceptance. In Bitcoin, pinning can target fee-bumping mechanisms, package limits, replace-by-fee rules, descendant limits, or transaction identifiers. Payment channels are especially sensitive when a party must confirm a time-critical transaction before a timelock expires.

Defenses depend on current relay policy and protocol construction, including anchor outputs, package relay, carefully scoped signatures, and sufficient fee control. Developers must test adversarial transaction graphs across common node versions. A transaction being valid and well-funded does not guarantee that mempool policy will admit the intended replacement package. Systems need idempotent processing keyed to stable transaction and business identifiers. Repeated callbacks, node disagreements, reorganization, and delayed receipts must not create duplicate credits or irreversible state transitions before the required network evidence is available. These records allow a later rescan to reconstruct the result when an endpoint, webhook, or local index becomes unreliable. Operational records should retain the raw transaction, network identifier, sender and destination, asset and amount, block reference, execution status, and observed timestamps.

Customer-facing status should describe what is known without overstating settlement. Unknown, pending, included, failed, replaced, and finalized conditions need separate handling, together with a recovery procedure for transactions whose observed state conflicts across providers.

Risk-control point: Transaction pinning weaponizes relay policy against fee bumping, so time-sensitive protocols need adversarially tested package and replacement strategies. Transaction pinning is an attack that exploits mempool or replacement rules to keep a desired transaction package from confirming or being fee-bumped.