/ 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 3.1.8 on iOS
Tested on: 2019-07-24
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.
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 0.0.52 on iOS
Tested on: 2018-09-25
Receiving support
- No notification
There are no incoming transaction notifications for this service.
- Received transaction labeled replaceable in list
Visually indicates 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 labeled replaceable in list
Visually indicates 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 and original transactions
Both the original transaction and replacement transactions are shown in the transaction list.
Usability
Click on a thumbnail for a larger image or to play its video.
Attempting Transaction Replacement - Bump transaction details confirmation. Notes “Previous fee:” field as well as language about bumping.
Attempting Transaction Replacement - Transaction list with replacement transaction on top. Bump fee available again. Show replaced transaction button shows as well.
Attempting Transaction Replacement - Transaction list with replacement transactions “show replaced” button clicked. NOTE while testing, I inadvertently bumped twice so 2 replacement transactions appear here.
Attempting Transaction Replacement - Original transaction as viewed from the “show replaced” list. “Double spend by txhash” field has “update” value.
Attempting Transaction Replacement - Replacement “bumped” transaction. “Double spend by txhash” field has “update” value.
Attempting Transaction Replacement - Subsequent bumping on the same transaction has a different “bump fee” context menu options. Also the context menu notes “fee already at 1-conf-estimate level”.
Receiving Replacement Transaction - Transaction List Screen. Notes RBF(“replaceable”) transaction as well as double spend transaction. The replacement transaction also shows up as separate.
Receiving Replacement Transaction - Transaction details for replacement transaction. No RBF note or double spend note. Does show “double spend by txhash” field which points to original transaction.
Receiving Replacement Transaction - Transaction details for replacement transaction. No RBF note or double spend note. Does show “double spend by txhash” field which points to original transaction.
Receiving Replacement Transaction - Transaction details for original transaction. No RBF note or double spend note. Does show “double spend by txhash” field which points to new replacement transaction.
Receiving Replacement Transaction - Transaction details for original transaction. No RBF note or double spend note. Does show “double spend by txhash” field which points to new replacement transaction.
Receiving Replacement Transaction - Transaction list after the replacement transaction confirms. “Original” transaction doesn’t appear.
Receiving Replacement Transaction - Transaction details for confirmed, replacement transaction. No note of double spend or RBF. “double spend by txhash” field disappears.