/ 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 0.91.1 on Linux
Tested on: 2020-10-29
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.
The BlockSettle Terminal supports all address types. Users may hold/view/operate multiple wallets and can select the address type they wish to generate. The overview displays all wallets, address paths, and addresses.
The BlockSettle Terminal defaults to native bech32 segwit when the user generates an address.
The BlockSettle Terminal displays the generated native bech32 segwit address
The BlockSettle terminal can send to native bech32 segwit addresses
The change address defaults to native bech32 segwit addresses, however, it is manually selectable by the user
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.91.1 on Linux
Tested on: 2020-10-29
Receiving support
- Notification notes RBF
Notification of incoming transaction notes that the transaction signals RBF.
- Received transaction labeled replaceable in list
Visually indicates that an incoming transaction has signaled RBF.
- Received transaction labeled replaceable in transaction details
Visually indicates 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
- 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 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.
Desktop notification includes RBF signaling
Transaction details includes RBF signaling
Transaction List includes RBF signaling
The transaction list displays the new incoming transaction, as well as the new outgoing transaction
The transaction overview includes RBF signaling
The transactions details include RBF signaling
The create transaction dialog has RBF signaling enabled by default
The RBF function can be selected by right-clicking on an RBF eligible transaction
The RBF dialog pre-populates the existing output by default
The RBF dialog allows the user to replace/change/remove the output(s) to create a new transaction