1ma
commented
11 months ago I like this idea in principle of course, but my understanding is that there are lots of ways to do data envelopes on bitcoin transactions, OP_0 IP_IF is just the most convenient to the spammers right now.
For an ordistroyer fork to be conclusively effective you would need to account for all the theoretically possible data envelopes in the new rule, which doesn't seem a trivial thing to figure out.
This is why I've always preferred standardness rules. In theory they can be deployed quickly and evolved as necessary without much hassle. Going multiple times through the consensus building for activating successive variations of an Ordistroyer soft fork, on the other hand... oof.
Please describe the feature you'd like to see added.
I'd like to turn the standardness rule introduced by the ordisrespector into a consensus rule, I've dubbed "ordistroyer". I'll pick a block height to activate it at, and after that block, any blocks including ordinals will be rejected by the node. This would preserve the existing blockchain in the ordistroyer network, but from that point would restore bitcoin's purpose as a ledger of sats.
Is your feature related to a problem, if so please describe it.
No response
Describe the solution you'd like
No response
Describe any alternatives you've considered
No response
Please leave any additional context
No response