The present “debate”, and even calling it that’s me being wildly over-charitable, over OP_RETURN is without doubt one of the most absurd conditions I’ve ever seen on this area. I say that as somebody who has been in Bitcoin for over a decade. Even the blocksize wars don’t maintain a candle to this, at the very least when it comes to utter absurdity. Not less than again then it was centered round an precise engineering disagreement. 

I wish to touch upon one factor at present although. Cease directing your irrational rage and nonsense on the fallacious targets. You aren’t mad at Bitcoin Core, you’re mad at me. 

NO ONE can alter your node besides you. NO ONE could make you obtain a model of Bitcoin Core that modifications one thing besides you. Finish of story. Full cease. YOU are chargeable for your node, what it enforces, and what it does. You and also you alone.

All the challenge of eradicating the OP_RETURN restrict has nothing to do with Bitcoin Core “forcing” something on anybody. They actually can’t try this, it’s unimaginable to. All they’re doing with this pull request is acknowledging the truth of individuals like me. They’re making a logical engineering determination within the face of a minority of customers who won’t run shoppers imposing present OP_RETURN limits. 

I’ll by no means run a node that’s configured to implement these limits. Ever. It’s that straightforward. I don’t suppose it’s my job, or my place, or my proper to arbitrate or resolve what forms of consensus legitimate transactions different customers make. Interval. If it’s consensus legitimate and pays a price, it’s not my enterprise. In case you have an issue with transactions which might be consensus legitimate, handle that downside the place it ought to be, on the consensus degree. As somebody is so well-known for quipping continuously on this nonsense: use the appropriate instrument for the job. 

Bitcoin is meant to be a permissionless system, and that truly means one thing to me. 

So long as folks like me won’t implement the relay filter on OP_RETURN that many individuals are upset with, your use of that filter is pointless. It accomplishes nothing. It doesn’t cease these transactions from being relayed throughout the community. It doesn’t cease them from getting mined in blocks. It accomplishes nothing. It’s a pointless function from an engineering perspective.

All Core builders proposed doing is to acknowledge this actuality that’s solely outdoors of their management. 

Core builders will not be those configuring datacarriersize to the utmost restrict, or working LibreRelay, or constructing the personal miner APIs/mempools that enable direct entry to blockspace bypassing public mempools. They’ve nothing to do with any of this. 

All they’re doing is reacting to the actions of others to mitigate hurt to the community. 

If you wish to get offended about this, that’s your prerogative. If you wish to “take motion” towards the individuals who created this case, that can also be your prerogative. However direct it within the applicable course: the opposite customers of Bitcoin who’ve created this case that builders should react to. 

Don’t be a chickenshit directing your rage at a celebration not chargeable for this case simply since you suppose they’re a neater goal. Be a person and direct your anger the place it belongs

This text is a Take. Opinions expressed are solely the creator’s and don’t essentially replicate these of BTC Inc or Bitcoin Journal.