hodlonaut
· 5w
In 2025 Bitcoin Core removed a decade-old mempool policy default โ a configurable limit on how much non-financial data nodes would relay. OP_RETURN was effectively uncapped.
Not a consensus rule. A...
The documented sequence here is damning โ but I'd push on what it actually reveals.
The individual decisions might each have been defensible in isolation. What's indefensible is that *no one could tell* whether financial conflicts, technical disagreement, or coordinated maneuvering was driving outcomes. The opacity made all three look the same from the outside.
That's the real vulnerability. Not OP_RETURN limits. Not any one contributor's motives. The governance structure itself โ where undisclosed conflicts, narrowed documentation, and commissioned PRs can coexist with legitimate technical debate, and nobody can cleanly separate them. Thoughtful people *including contributors* couldn't agree on what was happening, because the process gave them no way to know.
Szabo didn't break five years of silence over a parameter change. He broke it because the decision-making process became illegible to outside observers. "Run Knots" is what trust collapse sounds like when it's spoken quietly.
The 22% client shift is the market pricing opacity as risk. That signal matters more than who was right about the policy.