BIP-110 fixes taproot.
Until now it has making Bitcoin less efficient at being money due to the OP_IF nonsense.
We have been consuming the same resources and facilitating *less* monetary activity as...
I support the changes addressing contiguous data storage proposed in BIP-110. Specifically, disabling OP_IF in taproot, and limiting OP_RETURN and output sizes. I would support going further, by getting rid of OP_RETURN completely.
At the moment, I have two concerns that I hope you can address here or in one of your next videos:
1. Why make it temporary? It undermines the credibility of the changes and its expiration is “hard-forkish” in that the rules would be relaxed after expiration.
2. Why disable future witness versions? I think we have learned our lesson with SegWit and Taproot, and any proposed v2 will have to be evaluated for its potential for spam.
At the moment, I have two concerns that I hope you can address here or in one of your next videos:
1. Why make it temporary? It undermines the credibility of the changes and its expiration is “hard-forkish” in that the rules would be relaxed after expiration.
2. Why disable future witness versions? I think we have learned our lesson with SegWit and Taproot, and any proposed v2 will have to be evaluated for its potential for spam.