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

  • Notification does not note RBF
    Notification of incoming transaction does not note that the transaction is RBF signaling
  • 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 unconfirmed transactions
    Neither the original nor replacement transactions are shown in the transaction list. Most likely unconfirmed transactions are not supported

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 with fee options expanded. No RBF options.
Sending RBF Transaction - Default send transaction screen with fee options expanded. No RBF options.

Sending RBF Transaction - Send confirmation screen. Fee noted. No RBF note. Note Transaction was not sent with RBF flag enabled.
Sending RBF Transaction - Send confirmation screen. Fee noted. No RBF note. Note Transaction was not sent with RBF flag enabled.

Bumping RBF Transaction - Transaction list screen showing sent transaction. No RBF options. Note BitGo uses the Smartbit explorer to show transaction details.
Bumping RBF Transaction - Transaction list screen showing sent transaction. No RBF options. Note BitGo uses the Smartbit explorer to show transaction details.

Receiving RBF Transaction - Unconfirmed transactions do not appear in BitGo transactions list.
Receiving RBF Transaction - Unconfirmed transactions do not appear in BitGo transactions list.

Receiving RBF Transaction - Incoming transaction email. No RBF note.
Receiving RBF Transaction - Incoming transaction email. No RBF note.

Receiving Bumped RBF Transaction - Since no unconfirmed transaction appear, neither original nor bumped show until the bumped confirms.
Receiving Bumped RBF Transaction - Since no unconfirmed transaction appear, neither original nor bumped show until the bumped confirms.