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: on web

Tested on: 2019-07-26

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.

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

Trezor Wallet 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: on web

Tested on: 2018-11-08

Receiving support

• No notification
  There are no incoming transaction notifications for this service.

• 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 transaction only
  Only the replacement transaction is shown in the transaction list. No original transaction is 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. Fee options. No RBF options. Transaction not sent RBF.

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 - Trezor Wallet’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.