How to cancel a pending transaction on Trezor? (RBF feature)

Understanding RBF in Trezor Wallets

1. Replace-by-Fee (RBF) is a Bitcoin protocol feature that allows users to replace an unconfirmed transaction with another one that pays a higher fee.

2. Trezor Suite supports RBF-enabled transactions when sending BTC from native SegWit or legacy addresses.

3. The RBF flag must be explicitly enabled before broadcasting the original transaction — it cannot be added retroactively to a non-RBF transaction.

4. Once activated, the wallet constructs the transaction with the BIP125 signaling field set, making it eligible for replacement by miners and compatible nodes.

5. RBF status is visible in Trezor Suite under transaction details as “Replaceable” or “RBF-enabled”.

Step-by-Step RBF Transaction Replacement

1. Open Trezor Suite and navigate to your Bitcoin account.

2. Locate the pending transaction in your history and verify its RBF status — only RBF-marked transactions can be replaced.

3. Click the three-dot menu next to the transaction and select “Speed up”.

4. Adjust the fee slider to increase the sat/vB rate above current mempool minimums; Trezor Suite displays real-time fee estimates.

5. Confirm the new transaction on your Trezor device — the device will show both the original and replacement outputs before signing.

Limitations and Constraints

1. RBF does not work for transactions sent from multisig wallets managed via Trezor unless all signers support BIP125 signaling.

2. Transactions already included in a block — even if later orphaned — cannot be replaced using RBF.

3. Some third-party services like exchanges disable RBF by default and may reject replacement broadcasts.

4. If the original transaction receives one confirmation, RBF becomes technically irrelevant as consensus locks it into the chain.

5. Trezor hardware itself does not store or track RBF state — this logic resides entirely in Trezor Suite’s client-side transaction builder.

Fee Estimation and Mempool Behavior

1. Trezor Suite pulls fee data from multiple public mempool APIs including mempool.space and Blockstream Green’s estimator.

2. Fee suggestions are categorized as “fast”, “medium”, and “slow”, each tied to probabilistic confirmation time windows.

3. Manual fee input accepts values between 1 and 1000 sat/vB, though values below 5 sat/vB rarely propagate reliably during congestion.

4. Transaction size in virtual bytes (vB) is calculated dynamically based on input count, signature type, and witness data — larger UTXOs increase vB more than smaller ones.

5. A replacement transaction must signal higher total fee, not just higher fee rate — otherwise miners ignore it per BIP125 rules.

Frequently Asked Questions

Q: Can I cancel a non-RBF Bitcoin transaction using Trezor?Only if it remains unconfirmed and you control all inputs — then you may attempt CPFP (Child-Pays-For-Parent) by sending a dependent transaction with elevated fees. Trezor Suite does not automate CPFP.

Q: Does enabling RBF reduce my transaction privacy?Yes. RBF signals intent to replace, linking related transactions in mempool explorers. Observers can infer wallet behavior patterns from successive replacements.

Q: Why does Trezor Suite sometimes gray out the “Speed up” option?This occurs when the transaction lacks the BIP125 opt-in flag, has received at least one confirmation, or originates from an address type incompatible with RBF signaling (e.g., P2TR).

Q: What happens if both original and replacement transactions get confirmed?Miners follow consensus rules: only one version enters the blockchain. The network discards the lower-fee version upon seeing the higher-fee broadcast — no double spend occurs.