Segwit | Replace-by-Fee

Segwit Addresses

What are segwit addresses? Transactions that spend bitcoins secured by segregated witness (segwit) use less block weight than equivalent non-segwit (legacy) transactions, allowing segwit transactions to pay less total fee to achieve the same feerate as legacy transactions.

Tested: on web

Tested on: 2019-04-12

Receive support

  • Allows receiving to P2SH-wrapped segwit
    Allows the generation of P2SH-wrapped (either P2WPKH or P2WSH) segwit receiving addresses.
  • Does not allow receiving to bech32 segwit addresses
    Does not allow the generation of bech32 native (either P2WPKH or P2WSH) segwit receiving addresses.
  • Default receiving address is P2SH-wrapped P2WPKH
    This service generates P2SH-wrapped P2WPKH segwit receiving addresses by default.

Send support

  • Allows sending to bech32 P2WPKH addresses
    Allows sending to bech32 P2WPKH native segwit addresses.
  • Allows sending to bech32 P2WSH addresses
    Allows sending to bech32 P2WSH native segwit addresses.
  • Creates bech32 change addresses
    When sending, generates bech32 (either P2WPKH or P2WSH) segwit change addresses.

Usability

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

Bitrefill allows P2SH-wrapped segwit deposits. No bech32 option available.
Bitrefill allows P2SH-wrapped segwit deposits. No bech32 option available.

Bitrefill can send to bech32 native addresses. Change address is also bech32.
Bitrefill can send to bech32 native addresses. Change address is also bech32.


Replace-by-Fee (RBF)

What is 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.

Tested: on web

Tested on: 2018-11-06

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 transaction(s) 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.
  • No replacements in transaction list
    Because no transaction replacement is possible in the user interface, 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 Transaction - Default send transaction screen. No RBF info. Transaction was sent via RBF.
Sending Transaction - Default send transaction screen. No RBF info. Transaction was sent via RBF.

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


Receiving Transaction Signaling RBF - 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 Transaction Signaling RBF - 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 Replacement Transaction - After replacement transaction was broadcast, both transactions show up as pending. Stayed as pending even after the replacement transaction had 6+ confirmations.
Receiving Replacement Transaction - After replacement transaction was broadcast, both transactions show up as pending. Stayed as pending even after the replacement transaction had 6+ confirmations.


Receiving Replacement 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 Replacement Transaction - At some point in the next day, the original transaction was marked failed and replacement transaction was credited to account and marked complete.