Why is `SIGHASH_ALL` allowed in taproot when `SIGHASH_DEFAULT` is more efficient?

The existence of SIGHASH_DEFAULT makes SIGHASH_ALL redundant for Taproot, since both produce the same behavior — except SIGHASH_DEFAULT saves a byte by being implicit.

Given Bitcoin’s usual focus on minimizing blockspace usage (e.g. x-only pubkeys, minimal ScriptSig rules), why isn’t there a consensus or policy rule to disallow or discourage SIGHASH_ALL in Taproot signatures?

I’m not suggesting it’s a bad design choice — I just want to understand the rationale behind allowing the redundant form.



from Recent Questions - Bitcoin Stack Exchange https://ift.tt/3HkUf0R
via IFTTT

Popular posts from this blog

How to compute MAST commit bytes in bitcoin payment?

Image
The hash digests used to create the commitments are each 32 bytes, so proving that a spend of Figure 7-6 is authorized (using a merkle tree and the particular conditions) and authenticated (using signatures) uses 383 bytes. By comparison, the same spend without a merkle tree (i.e., providing all possible authorization conditions) uses 412 bytes. Can anyone explain how to compute 383 bytes and 412 bytes? Thanks! from Recent Questions - Bitcoin Stack Exchange https://ift.tt/M2lri0K via IFTTT
Read more

Isit possible to swap my MBTC into BTC

I have a question. I was sent some bitcoin about 10 years ago on my bitcoin wallet app. I just found it today and i'm a little confused whether it is a wrapped version or the original bitcoin because there is a M infront of the BTC. Please can someone clarify from Recent Questions - Bitcoin Stack Exchange https://ift.tt/oj8vRHf via IFTTT
Read more

Anyone help with some tbtc?

Anyone help with some tbtc? Need a quite large amount for testing. Here is my address : tb1pve2jcvzmh6vjvlk6qnpae0yd2dsv96jp2cswaszazmkargxrgmgqu0p6ul from Recent Questions - Bitcoin Stack Exchange https://ift.tt/ltVf39I via IFTTT
Read more