/ 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 2.23.0 on Android
Tested on: 2022-10-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.
- Does not create bech32 change addresses
When sending, does not generate bech32 (either P2WPKH or P2WSH) segwit change addresses.
Usability
Click on a thumbnail for a larger image or to play its video.
Edge generates only
Edge allows sends to segwit v0 native bech32 addresses.
Edge allows the creation of “Segwit” and “no Segwit” wallets. The “Segwit” wallets use P2SH-wrapped P2WPKH addresses. Both wallet types can send to segwit v0 addresses.
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 2.23.0 on Android
Tested on: 2022-10-12
Receiving support
- Notification does not note RBF
Notification of incoming transaction does not note 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 and original transactions
Both the original transaction and replacement transaction(s) are shown in the transaction list.
Sending support
- Does not signal BIP125 replacability when sending transactions
Does not allow sending of BIP125 opt-in-RBF transactions in the interface.
- Not tested: Does transaction list show whether sent transactions signal RBF?
We were not able to test this because sending a BIP125 signaling transaction is not supported.
- Not tested: Does transaction details page show whether received transaction signals RBF?
We were not able to test this because sending a BIP125 signaling transaction is not supported.
- Not tested: Are replacement and original sent transactions displayed?
We were not able to test this because sending a BIP125 signaling transaction is not supported.
Usability
Click on a thumbnail for a larger image or to play its video.
Sending RBF Transaction - Default Send screen. No option for RBF.
Sending RBF Transaction - Context menu for send transaction show mining fee options.
Sending RBF Transaction - Mining fee options dialog.
Sending RBF Transaction - Mining fee custom dialog.
Bumping RBF Enabled Transaction - Mining fee custom dialog.
Receiving RBF Transaction - Receiving RBF enabled transaction. No RBF Flag.
Receiving RBF Transaction - Transaction details for received RBF transaction. Links to blockchair.com explorer.
Receiving Bumped RBF Transaction - Transaction list with top 2 transactions being the original and bumped RBF transaction. No RBF flag. Note that the balance only went up by the value of one of the transactions.