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: version 7.26 on Android

Tested on: 2019-11-06

Receive support

  • Does not allow receiving to P2SH-wrapped segwit
    Does not allow the generation of P2SH-wrapped (either P2WPKH or P2WSH) segwit receiving addresses.
  • Allows receiving to bech32 segwit addresses
    Allows the generation of bech32 native (either P2WPKH or P2WSH) segwit receiving addresses.
  • Default receiving address is bech32 P2WPKH
    This service generates bech32 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.


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

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.

We have not yet tested Bitcoin Wallet for RBF capabilities.