Segwit | Replace-by-Fee

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 21.4.1 on macOS

Tested on: 2021-04-13

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.
  • Allows receiving to bech32m addresses
    Allows the generation of bech32m (P2TR) 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.
  • 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.

By default, Trezor generates a bech32 native P2WPKH receive addresses. There is also an option to generate a legacy P2SH-wrapped-P2WPKH and P2PKH addresses.
By default, Trezor generates a bech32 native P2WPKH receive addresses. There is also an option to generate a legacy P2SH-wrapped-P2WPKH and P2PKH addresses.

Trezor Suite allows for sending to any bech32 segwit v0 address.
Trezor Suite allows for sending to any bech32 segwit v0 address.


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 21.4.1 on macOS

Tested on: 2021-04-13

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 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 replaceability 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 labeled replaceable in transaction details
    Visually indicates 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.

Sending Transaction - Send transaction screen. Fee options. RBF options. By default, transaction sent as RBF.
Sending Transaction - Send transaction screen. Fee options. RBF options. By default, transaction sent as RBF.

Attempting Transaction Replacement - Transaction list screen showing sent transaction. No bumping options.
Attempting Transaction Replacement - Transaction list screen showing sent transaction. No bumping options.


Receiving Transaction Signaling RBF - Incoming transaction list. No RBF flag.
Receiving Transaction Signaling RBF - Incoming transaction list. No RBF flag.

Receiving Transaction Signaling RBF - Trezor Suite's block explorer for incoming RBF transaction. Does not note that the transaction has signaled RBF.
Receiving Transaction Signaling RBF - Trezor Suite’s block explorer for incoming RBF transaction. Does not note that the transaction has signaled RBF.


Receiving Replacement Transaction - replacement transaction replaces original transaction. Block explorer no longer finds original transaction.
Receiving Replacement Transaction - replacement transaction replaces original transaction. Block explorer no longer finds original transaction.