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.12.0 on macOS
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.
- 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.
Usability
Click on a thumbnail for a larger image or to play its video.
Ledger Live can generate bech32 native addresses. Note this depends on how your wallet was initial created. Bech32 support is new in Ledger Live.
Ledger Live can send to all variants of bech32 addresses for v0.
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.2.0 on macOS
Tested on: 2018-10-11
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 original transaction only
Only the original transaction is shown in transaction list. Replacement transactions are not shown.
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 Transaction - Send transaction screen does not allow for RBF. Fee options are available. No RBF options in settings.
Attempting Transaction Replacement - Transaction details screen. No RBF fee bumping supported.
Receiving Transaction Signaling RBF - Transaction list screen. No RBF flag.
Receiving Transaction Signaling RBF - Transaction details screen. No RBF flag.
Receiving Replacement Transaction - Transaction list screen does not show the replacement transaction. Only the original. Even after the new, replacement transaction received 6+ confirmations.
Receiving Transaction Signaling RBF - Internal database error shows conflicting bitcoin inputs. Original transaction remains unconfirmed. Ticket opened with Ledger to address. Update - Solution was to clear cache in app.