Replace-by-Fee (RBF)

An unconfirmed transaction can be replaced by another version of the same transaction that spends the same inputs. Most full nodes support this if the earlier transaction enables BIP125 signaling and the replacement transaction increases the amount of fee paid. In terms of block chain space used, this is the most efficient form of fee bumping.

Receiving support

  • No notification
    There are no incoming transaction notifications for this service
  • Received transaction not labeled replaceable in list
    Does not visually indicate that an incoming transaction has signaled RBF
  • Received transaction not labeled replaceable in transaction details
    Does not visually indicate that a received transaction has signaled RBF when viewing the transaction details
  • Shows replacement and original transactions
    Both the original transaction and replacement transactions are shown in the transaction list

Sending support

  • Signals BIP125 replacability when sending transactions
    Allows sending of BIP125 opt-in-RBF transactions in the interface
  • Sent transaction not labeled replaceable in list
    Does not visually indicate that an outgoing transaction has signaled RBF
  • Sent transaction not labeled replaceable in transaction details
    Does not visually indicate that a sent transaction has signaled RBF when viewing the transaction details
  • Not tested
    We either didn’t test this or could not appropriately determine the results

Usability

Click on a thumbnail for a larger image or to play its video.

Sending RBF Transaction - Default send transaction screen. No RBF info. Transaction was sent via RBF.
Sending RBF Transaction - Default send transaction screen. No RBF info. Transaction was sent via RBF.

Bumping RBF Transaction - Transaction list screen. No way to manually bump the transaction. Was sent RBF.
Bumping RBF Transaction - Transaction list screen. No way to manually bump the transaction. Was sent RBF.

Receiving RBF Transaction - No incoming transactions show initially during original transaction. This delay could have been related to delays in relaying the transaction in the Bitcoin network.
Receiving RBF Transaction - No incoming transactions show initially during original transaction. This delay could have been related to delays in relaying the transaction in the Bitcoin network.

Receiving Bumped RBF Transaction - After replacement transaction was broadcast, both transactions show up as pending. Stayed as pending even after the replacement transaction confirmed 6+.
Receiving Bumped RBF Transaction - After replacement transaction was broadcast, both transactions show up as pending. Stayed as pending even after the replacement transaction confirmed 6+.

Receiving Bumped RBF Transaction - At some point in the next day, the original transaction was marked failed and replacement transaction was credited to account and marked complete.
Receiving Bumped RBF Transaction - At some point in the next day, the original transaction was marked failed and replacement transaction was credited to account and marked complete.