Cc @Peter Todd

Nice! Common sense prevailed... 😅🙌

Finally common sense prevailed..! 🙌🧡

Never forget

What a pain in the ass this

Has it though? I interpret this to mean that by the default, settings will be structured in such a manner to support the inscription spam. It’s just that now, we node operators can manually change a certain config setting to opt out of that crap. 💩 But those who don’t opt out will happily relay and store the spam by default. Or maybe I’m missing something?

Well if the PR had passed then all node operators would have 0 settings and choice to filter anything... So any 💩 would be allowed by default by all node operators without any way to change any settings.

Core leaving OP_RETURN limits “configurable” isn’t helping anyone… it’s self-preservation disguised as neutrality. They won’t endorse metadata, and they also won’t touch the real problem: unbounded witness data bloating validation. -Miners already ignore the OP_RETURN limits. -Smaller miners with slower or less-optimized connections are still more likely to have their blocks orphaned. -Users get no clarity. -Node runners get no relief. I know everyone’s sick of this already but the discussion shouldn’t end here… nevent1qqsz7q2cyxuawp0n2vqawde64n3t2f666wl2x9055t8enm534cdqd8qp2emhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtmwwp6kyvt2dq68zafjvu6k2dpewduhyamgxgunxufcwyunq7r9ddk8vercxsmhqmn2x4m8jcmpxf6xkmr2v4jrqwr4wvcxxar2xe4sds20mz

The larp is finally over @Detective Deft Defector 😅 I can stop crashing out now nevent1qqsz7q2cyxuawp0n2vqawde64n3t2f666wl2x9055t8enm534cdqd8qp2emhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtmwwp6kyvt2dq68zafjvu6k2dpewduhyamgxgunxufcwyunq7r9ddk8vercxsmhqmn2x4m8jcmpxf6xkmr2v4jrqwr4wvcxxar2xe4sds20mz