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
- Does not show transaction details
This service does not show transaction details natively. Usually this means the service links off to a block explorer for 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
- Does not show transaction details
This service does not show transaction details natively. Usually this means the service links off to a block explorer for transaction details.
- Shows replacement transaction only
Only the replacement transaction is shown in the transaction list. No original transaction shown
Usability
Click on a thumbnail for a larger image or to play its video.