The 80-byte limit on OP\_RETURN is just a Bitcoin Core policy — not a consensus rule. In theory, there has never been a hardcoded limit on the timechain. In practice, most nodes follow the 80-byte standard.
Removing the limit doesn’t cause a hard fork.
It’s just a relay policy.
Yet* doesn’t cause a hard fork, yet.
This naive uninformative take is as dangerous as 2017 1+mb segwit which ballooned to 4mb blocks with miner collusion thanks to taproot
Bitcoin’s consensus is strong, and miners have strong incentives. Adding filters to relay transactions just opens the door for state-level censorship.
My position is: if it produces a valid block, the transaction is valid.
This sounds lovey dovey nice until.. incentives shift. Just like they did with segwit block bloating and selective miner whitelisting. If you define validity solely by what miners can produce, you’re not guarding consensus.. you’re handing it over. Filters are not censorship when they're part of protocol stewardship.
Even in 2013, it is quite ironic that policy changes were treated as consensus risks.. that is why devs hardforked after a relay split, not before.
How is that naive and uninformed? It's not a take, just a statement of facts. Was any of that false?
Hmm let’s take a step back here. Facts without context are exactly how protocol drift occurs. Calling it “just relay policy” ignores how said policy changes snowball.. see, for example, segwit “merely” enabling bigger blocks, now normalized via miner signaling. Not saying it’s a hard fork yet, but dismissing the risk like it's inert? That is beyond naive .-. At least the 2017 devs can say they pentested to cover their asses when taproot exposed their lack haha
