Keep an original-and-replacement ledger for a Bitcoin RBF payment

Keep an original-and-replacement ledger for a Bitcoin RBF payment

A Bitcoin fee bump creates a conflicting transaction that spends one or more of the same inputs. It does not edit the original hash, and a wallet's replaced label is not the same as an on-chain cancellation.

Bitcoin Core documents current node mempool replacement policy, including fee and feerate requirements. Individual nodes, miners and wallets can expose different views during propagation.

Create the conflict set

Record the original hash and every candidate replacement with broadcast time and wallet action used. Editing one row destroys the evidence that multiple versions existed.

Link transactions by shared spent outpoints rather than similar wallet descriptions. The documentation supports treating originals and replacements as distinct transactions and checking conflicting inputs, absolute fees and mempool policy.

Verify destination and amount across versions before assuming the fee bump preserved the business payment. A replacement can change outputs while still conflicting with the original. Cancel the signing step if the recipient or value differs unexpectedly.

Compare recipient outputs

Verify destination and amount across versions before assuming the fee bump preserved the business payment. A replacement can change outputs while still conflicting with the original.

Cancel the signing step if the recipient or value differs unexpectedly. It cannot guarantee propagation, predict which miner will include a transaction, preserve the intended recipient, reverse a confirmed payment or explain every wallet interface.

Write absolute fee, virtual size and feerate for each version in separate columns. A higher feerate alone does not summarize every current replacement rule. Use wallet estimates as estimates and avoid promising a confirmation deadline.

Separate fee from feerate

Write absolute fee, virtual size and feerate for each version in separate columns. A higher feerate alone does not summarize every current replacement rule.

Use wallet estimates as estimates and avoid promising a confirmation deadline. Maintain every hash in one conflict set, compare outputs before approval and recognize only the confirmed transaction as the chain outcome.

Check more than one reputable node or explorer and timestamp each mempool observation. A missing transaction can reflect eviction or indexing delay rather than final cancellation. Do not rebroadcast secrets or submit a seed phrase to a tracing service.

Observe propagation cautiously

Check more than one reputable node or explorer and timestamp each mempool observation. A missing transaction can reflect eviction or indexing delay rather than final cancellation.

Do not rebroadcast secrets or submit a seed phrase to a tracing service. Fee pressure is not a reason to duplicate a gambling deposit. Keep essential money outside uncertain payment attempts and wait for reconciliation.

Identify the hash included in a block, verify its outputs and give that evidence to the receiver. Other conflicting hashes should remain in the incident log as unconfirmed alternatives. Never send another principal amount merely to make support notice the case.

Close on confirmation

Identify the hash included in a block, verify its outputs and give that evidence to the receiver. Other conflicting hashes should remain in the incident log as unconfirmed alternatives.

Never send another principal amount merely to make support notice the case. Bitcoin Core documents current node mempool replacement policy, including fee and feerate requirements. Individual nodes, miners and wallets can expose different views during propagation.

Record the original hash and every candidate replacement with broadcast time and wallet action used. Editing one row destroys the evidence that multiple versions existed. Link transactions by shared spent outpoints rather than similar wallet descriptions.

What the official source supports

Bitcoin Core current mempool replacement policy documentation: The documentation supports treating originals and replacements as distinct transactions and checking conflicting inputs, absolute fees and mempool policy.

Where the source stops

It cannot guarantee propagation, predict which miner will include a transaction, preserve the intended recipient, reverse a confirmed payment or explain every wallet interface.

Make the documented decision

Maintain every hash in one conflict set, compare outputs before approval and recognize only the confirmed transaction as the chain outcome.

Fee pressure is not a reason to duplicate a gambling deposit. Keep essential money outside uncertain payment attempts and wait for reconciliation.

Build the final verification sheet

A Bitcoin fee bump creates a conflicting transaction that spends one or more of the same inputs. It does not edit the original hash, and a wallet's replaced label is not the same as an on-chain cancellation. Maintain every hash in one conflict set, compare outputs before approval and recognize only the confirmed transaction as the chain outcome. Fee pressure is not a reason to duplicate a gambling deposit. Keep essential money outside uncertain payment attempts and wait for reconciliation.

Link transactions by shared spent outpoints rather than similar wallet descriptions. Cancel the signing step if the recipient or value differs unexpectedly. Use wallet estimates as estimates and avoid promising a confirmation deadline. Do not rebroadcast secrets or submit a seed phrase to a tracing service. Never send another principal amount merely to make support notice the case.

Run a final evidence review before acting

Bitcoin Core documents current node mempool replacement policy, including fee and feerate requirements. Individual nodes, miners and wallets can expose different views during propagation. A complete review should answer each named question in order: Create the conflict set; Compare recipient outputs; Separate fee from feerate; Observe propagation cautiously; Close on confirmation. Keep an unanswered item visibly unresolved instead of filling it with a guess. It cannot guarantee propagation, predict which miner will include a transaction, preserve the intended recipient, reverse a confirmed payment or explain every wallet interface.

Create the conflict set requires this concrete check: Record the original hash and every candidate replacement with broadcast time and wallet action used. Link transactions by shared spent outpoints rather than similar wallet descriptions. Compare recipient outputs requires this concrete check: Verify destination and amount across versions before assuming the fee bump preserved the business payment. Cancel the signing step if the recipient or value differs unexpectedly. Separate fee from feerate requires this concrete check: Write absolute fee, virtual size and feerate for each version in separate columns. Use wallet estimates as estimates and avoid promising a confirmation deadline. Observe propagation cautiously requires this concrete check: Check more than one reputable node or explorer and timestamp each mempool observation. Do not rebroadcast secrets or submit a seed phrase to a tracing service. Close on confirmation requires this concrete check: Identify the hash included in a block, verify its outputs and give that evidence to the receiver. Never send another principal amount merely to make support notice the case.

For more context on Bitcoin fee and replacement education, compare the named source with the responsible-play centre, the guide library and our editorial policy. SignalBet Guide referral links are disclosed, and compensation does not control sourcing, corrections or safety conclusions.