Why does not enable sighash default for non-taproot transaction(i.e. p2pkh, p2sh, p2wpkh, p2wsh)? I think it's great BIP341 adds sighash default to save a single byte, which could be huge in aggregate. As segwit v0 and legacy transactions still take a lot of portion, wouldn't it be good to enable sighash default for them? It's more efficient, and increases overall backward-compatiblity(without concern about malleability in my humble opinion).
Enable sighash default option for non-taproot(or tapscript) spend? #29857
issue ChrisCho-H opened this issue on April 11, 2024-
ChrisCho-H commented at 4:23 PM on April 11, 2024: none
- ChrisCho-H added the label Feature on Apr 11, 2024
-
sipa commented at 4:29 PM on April 11, 2024: member
That's not possible without a hardforking consensus change, which would need extensive discussion and widespread agreement among the community.
Furthermore, anyone who would be interested in the byte savings enabled by such a change could instead just migrate to using taproot, which would result in far larger savings for most users.
- achow101 closed this on Apr 11, 2024
- bitcoin locked this on Apr 11, 2025
Contributors
Labels