Topic: Basic questions about Taproot pros and cons vs Native Segwit (Read 100 times)
^The difference in size of a segwit and taproot TX is negligible and almost identical in single signature so using taproot just only to pay less fee isn't that great idea meanwhile if you're someone who uses multi sig the taproot is for you which saves more fee than segwit. Since it's not really concentrated on lowering the fee like segwit upgrade people never interested in switching to taproot and that's probably one of the reason why most Bitcoin users just stuck with segwit itself for efficient fee.
In practice, it's more complicated though. When you send Bitcoin to someone else, you usually can't force them to provide specific type of address (P2WPKH in this case). If you plan to receive Bitcoin from someone else, there's chance their wallet software doesn't support sending to P2TR address.
I understood it.It's only in hands of us to control if we send bitcoins in our non custodial wallet to another wallet of ours. If we send it to other people, things become harder and nearly out of control.
In forum, signature campaign managers have to force participants to use Bech32 address to save transaction fees in payment broadcast.
Adoption on Segwit Bech32 is better than Taproot Bech32m so I'd prefer to use Bech32 addresses for myself.
https://en.bitcoin.it/wiki/Bech32_adoption
https://txstats.com/d/000000007/bech32-statistics?orgId=1
https://txstats.com/d/000000055/taproot-statistics?orgId=1
If you plan to receive Bitcoin from someone else, there's chance their wallet software doesn't support sending to P2TR address.
Don't really know why the adoption is slower than the version 0 , I mean it should be more though its just a slight difference depending on the transaction...maybe that's the case then.I would speculate the fact SegWit use Bech32, while Taproot use Bech32m contribute to slower Taproot adaption.
Even most bitcoin wallets are supporting segwit version 0 but many centralized platforms like exchanges are not yet supporting it. Exchanges like Bybit, HTX, Bitget, BitMart, Mexc and many other exchanges are not supporting even segwit version 0 up till now.
If the transaction have the same inputs and outputs, native segwit transactions are of low fee. If the inputs are more with just one or fewer outputs, taproot transactions have lower fee. If the outputs are more and with just one or few outputs, native segwit transactions are more.
To understand about it more, read this: Pay-to-taproot (P2TR) transaction fee
Native segwit have less output vbyte while taproot has less input vbyte.
It is worth knowing that taproot is also segwit. What you referred to as segwit is referred to as segwit version 0 while taproot is referred to as segwit version 1.
Thank you for the link to the previous posts/discussion. Very good stuff to learn about.To understand about it more, read this: Pay-to-taproot (P2TR) transaction fee
Native segwit have less output vbyte while taproot has less input vbyte.
It is worth knowing that taproot is also segwit. What you referred to as segwit is referred to as segwit version 0 while taproot is referred to as segwit version 1.
Now I can make a better informed decision.
If you plan to receive Bitcoin from someone else, there's chance their wallet software doesn't support sending to P2TR address.
Don't really know why the adoption is slower than the version 0 , I mean it should be more though its just a slight difference depending on the transaction...maybe that's the case then.I would speculate the fact SegWit use Bech32, while Taproot use Bech32m contribute to slower Taproot adaption.
If you plan to receive Bitcoin from someone else, there's chance their wallet software doesn't support sending to P2TR address.
Don't really know why the adoption is slower than the version 0 , I mean it should be more though its just a slight difference depending on the transaction...maybe that's the case then.You can use this tool https://bitcoinops.org/en/tools/calc-size/ to discover transaction size of Native SegWit (P2WPKH) and Taproot (P2TR).
Use that tool or this tool https://jlopp.github.io/bitcoin-transaction-size-calculator/Compare to Segwit input, an input with Taproot is 10.5 vbyte smaller in size but in an output with Taproot, it is 12 vbyte larger. So depends on inputs and outputs for a transaction, Taproot can be cheaper than Segwit or more expensive.
In practice, it's more complicated though. When you send Bitcoin to someone else, you usually can't force them to provide specific type of address (P2WPKH in this case). If you plan to receive Bitcoin from someone else, there's chance their wallet software doesn't support sending to P2TR address.
You can use this tool https://bitcoinops.org/en/tools/calc-size/ to discover transaction size of Native SegWit (P2WPKH) and Taproot (P2TR). Personally i consider Taproot as good choice due to smaller input size, which lead to lower fee when you spend those Taproot UTXO. But since you mention PayJoin/CoinJoin, you probably want to use whatever address type used by other participant to make tracking more difficulty.
Thank you for the tool suggestion. Yeah I can see indeed Taproot is even better. I understand also your point about PayJoin/CoinJoin requiring similar address types, you're trying to tell that while P2TR is more efficient, since other participants don't use it as much for the time being it may not be the optimal choice.
As I was browsing around, I found this https://en.bitcoin.it/wiki/Bech32_adoption . In the past I noticed how somehow Electrum was able to construct UTXOs that were slightly cheaper than what Sparrow Wallet builds, but I will give Sparrow wallet again a try since they seem to have support for Taproot Multisig.
Thanks a lot.
You can use this tool https://bitcoinops.org/en/tools/calc-size/ to discover transaction size of Native SegWit (P2WPKH) and Taproot (P2TR).
Use that tool or this tool https://jlopp.github.io/bitcoin-transaction-size-calculator/Compare to Segwit input, an input with Taproot is 10.5 vbyte smaller in size but in an output with Taproot, it is 12 vbyte larger. So depends on inputs and outputs for a transaction, Taproot can be cheaper than Segwit or more expensive.
If the transaction have the same inputs and outputs, native segwit transactions are of low fee. If the inputs are more with just one or fewer outputs, taproot transactions have lower fee. If the outputs are more and with just one or few outputs, native segwit transactions are more.
To understand about it more, read this: Pay-to-taproot (P2TR) transaction fee
Native segwit have less output vbyte while taproot has less input vbyte.
It is worth knowing that taproot is also segwit. What you referred to as segwit is referred to as segwit version 0 while taproot is referred to as segwit version 1.
To understand about it more, read this: Pay-to-taproot (P2TR) transaction fee
Native segwit have less output vbyte while taproot has less input vbyte.
It is worth knowing that taproot is also segwit. What you referred to as segwit is referred to as segwit version 0 while taproot is referred to as segwit version 1.
You can use this tool https://bitcoinops.org/en/tools/calc-size/ to discover transaction size of Native SegWit (P2WPKH) and Taproot (P2TR). Personally i consider Taproot as good choice due to smaller input size, which lead to lower fee when you spend those Taproot UTXO. But since you mention PayJoin/CoinJoin, you probably want to use whatever address type used by other participant to make tracking more difficulty.
Hello everyone,
I hope this is the right section of the forum to be asking this. Here it goes:
I am interested in maybe moving over to taproot addresses for BTC layer 1 usage, how does it perform relative to Native Segwit addresses?
Are taproot transactions more efficient in terms of fee cost versus Segwit? How do they perform in basic format (1 input, 2 outputs) or are they more efficient if one uses taproot for coinjoins (many inputs and outputs)? I recall maybe hearing they can have better privacy capabilities when collaborating with others.
My current goals:
Find and use the most efficient fee method to do transactions with what layer 1 allows.
My ideal (if it is possible from what I think I have understood so far):
Batch all my future layer 1 transactions together with other people (PayJoin/CoinJoin) in order to achieve always a good combo of privacy (making chain analysis more difficult) and lower fees.
(because whenever I make L1 transactions, I am never in a rush, so it should allow for optimal fees and coordination)
I was left with the impression that taproot might allow people to summarize lots of data into one type of script (identical to other taproot transactions types).
Could you tell me what are the pros and cons of going from Native Segwit to Taproot?
Thank you!
I hope this is the right section of the forum to be asking this. Here it goes:
I am interested in maybe moving over to taproot addresses for BTC layer 1 usage, how does it perform relative to Native Segwit addresses?
Are taproot transactions more efficient in terms of fee cost versus Segwit? How do they perform in basic format (1 input, 2 outputs) or are they more efficient if one uses taproot for coinjoins (many inputs and outputs)? I recall maybe hearing they can have better privacy capabilities when collaborating with others.
My current goals:
Find and use the most efficient fee method to do transactions with what layer 1 allows.
My ideal (if it is possible from what I think I have understood so far):
Batch all my future layer 1 transactions together with other people (PayJoin/CoinJoin) in order to achieve always a good combo of privacy (making chain analysis more difficult) and lower fees.
(because whenever I make L1 transactions, I am never in a rush, so it should allow for optimal fees and coordination)
I was left with the impression that taproot might allow people to summarize lots of data into one type of script (identical to other taproot transactions types).
Could you tell me what are the pros and cons of going from Native Segwit to Taproot?
Thank you!
Jump to: