The existence of SIGHASH_DEFAULT makes SIGHASH_ALL redundant for Taproot, since each produce the identical habits — besides SIGHASH_DEFAULT saves a byte by being implicit.
Given Bitcoin’s traditional give attention to minimizing blockspace utilization (e.g. x-only pubkeys, minimal ScriptSig guidelines), why isn’t there a consensus or coverage rule to disallow or discourage SIGHASH_ALL in Taproot signatures?
I’m not suggesting it’s a nasty design selection — I simply need to perceive the rationale behind permitting the redundant kind.
