/ home / compatibility /
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 1.1.10 on macOS
Tested on: 2019-12-19
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.
- Not tested: Can bech32m transaction outputs be received?
We either didn’t test this or could not appropriately determine the results.
- 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.
- Allows sending to bech32m addresses
Allows sending to bech32m (P2TR) 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.
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: version 1.1.10 on macOS
Tested on: 2019-12-19
Receiving support
- Notification notes RBF
Notification of incoming transaction notes that the transaction signals RBF.
- 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 transaction only
Only the replacement transaction is shown in the transaction list. No original transaction is shown.
Sending support
- Does not signal BIP125 replaceability 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.
- Shows replacement transaction only
Only the replacement transaction is shown in the transaction list. No original transaction is shown.
Usability
Click on a thumbnail for a larger image or to play its video.