Ah, ok. That’s helpful. So, bigger sizes are already allowed. Core is just removing an arbitrary limit.
Discussion
There’s nothing arbitrary about it. Yes, it’s possible to make a larger op return and put it into a block, but it’s not trivial and if you check the number of larger than 80 bytes op returns, it’s only 0.01% of all the op returns since 2014. So the limit works as intended and now it’s nuked out of the water to make it easy for some VC pressure groups that want to turn Bitcoin into a crappier Ethereum.
thats because there is no active protocol that uses more, it is of course trivial to get around cores filter. i could do it right now with little effort. I could do it with 99% knots adoption. anyone claiming otherwise is delusional
But isn’t fair to ask why Core is removing the limit? Does removing it make the code base easier to read/maintain Like, what’s the rationale? Does keeping the limit hurt anything?
Didn’t you brag about working on Bitcoin since 2010? Sure, it’s easy for you. That doesn’t mean it’s easy for the 99% of spam enjoyers, most of whom are low tier clowns. Every filter adds opportunity cost. In other words, it raises the bar for on-chain spam, even for competent spammers, and the less technically capable you are, the steeper that bar gets.
it would be very easy for them, most of the time you can get around it by just pasting a tx into a web form. wow so difficult.