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

• No transaction list
  This service does not support listing of transactions

Sending support

• Does not signal BIP125 replacability when sending transactions
  Does not allow 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

• No replacements in transaction list
  Because no transaction replacement is possible, we could not test whether original or replacement sent transactions are shown after replacement

Usability

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

Sending RBF Transaction - Default send transaction screen. No RBF option.

Bumping RBF Enabled Transaction - Send transaction. Custom transaction fee option expanded. No bump fee option available.

Receiving RBF Transaction - Receiving RBF transaction. No RBF flag.