Since Taproot-Addresses have been launched for a while now, I've added a few lines including them in my overview:
Prefix | Category | Format |
________ | __________________________ | _______________________________________________________________________________ _____________ |
bc1p… | Taproot-Address | P2TR-bech32m (pay to tap root) |
...
bc1p… Addresses starting with bc1p, are
always SegWit.
....
Native SegWit or nested SegWit? After reading the lines above and finding out about the benefits of using SegWit addresses, you may be wondering what the differences are between a native SegWit address (bech32, starts with bc1q...) / Taproot Address (bech32m, starts with bc1p) compared to a nested SegWit address (P2WPKH-P2SH / P2WSH-P2SH, starts with 3....).
For us, it is important to know that using a native SegWit Address / Taproot-Address will result in even lower fees compared to a nested SegWit address.
Savings when sending from a nested SegWit address (3...) compared to a normal legacy address (1...) are 26% +.
Savings when sending from a native SegWit address (bc1q...) compared to a normal legacy address (1...) are 38% +.
Depending on the number of inputs to the address, savings are variable, with a higher number of inputs saving even more in percentages.
Added in November 2022: now, Taproot-Adresses (bc1p), are also available. In terms of saving fees, Taproot-Addresses are similarly effective as native SegWit Addresses (bc1q…). Savings compared to a normal legacy address (1...) are 38% +
A detailled calculation can be found
here, provided by Charles-Tim.
It's because of native SegWit and Taproot are technically very similar because native SegWit and Taproot are part of the Witness Programm (bech32 / bech32m).
...
All details are included in my OP.
In general, it's nice to see Bitcoin progressing from a technical point and I'm honored to include Taproot-Addresses in my OP.