Three outcome shapes visible in the data: a clean win for one side, a cascade win for the other, and a contested equilibrium where neither chain breaks through. General findings and useful frame for any contested fork. Full picture at UW BRI, July 13β17. #Bitcoin#softfork#UWBRI
One thing the simulation makes viscerally clear: a contested fork doesn't resolve gradually. It stalls... then it doesn't. Here's what the timeline actually looks like across 2,694 scenarios.
The race that matters in a contested soft fork isn't block-by-block. It's who reaches the difficulty adjustment first. That single event is a cascade trigger and it's why most observable action happens in a compressed window once that threshold is crossed.
A few people asked how the fork simulation actually works. The modeling choices matter, and I'd rather they be on the table before I start sharing results.
Here's the short version...
Then we vary what we can't know in advance, how adoption splits, how committed the pools are, how much conviction each actor has across thousands of scenarios on real Bitcoind nodes using warnet and watch what the network does. https://t.co/fOrGavCDzT
@TheGuySwann@jimmysong That's the gap simulation fills. Not a crystal ball, you can't predict what a new rule set gets used for. But whether a contested fork resolves cleanly or splits the chain is something you can study under today's conditions https://t.co/PSbBsHFDXa
@jimmysong Full methodology and findings at the University of Wyoming Bitcoin Research Institute workshop @rettlerb , July 13β17. Thread to follow. https://t.co/hULvR4aP0Q
Epistemic humility and quantitative analysis aren't opposites. You can hold both.
Watching the BIP110 debate, I keep seeing the same honest admission from people who know Bitcoin deeply: past forks only tell us so much about this one. We'll have to wait and see.
They're right that it's different. But "wait and see" isn't the only option.
What happens when brilliant developers try to predict complex human behavior? Usually, they get it wrong.
I read Jimmy Songβs essay "On Overconfidence" today, and it prompted some heavy reflection. Itβs easy to get caught up in our own projections, but history shows that complex systems rarely behave the way we expect.
I break down my perspective on the episode.
@TheGuySwann@jimmysong To be clear, this isn't guessing, it's testing. You take structured assumptions about how users might influence the system, run each one, and ask whether any of them actually moves the outcome. Keeping the assumptions transparent and explicit.
@jimmysong Full methodology and findings at the University of Wyoming Bitcoin Research Institute workshop @rettlerb , July 13β17. Thread to follow. https://t.co/hULvR4aP0Q
Epistemic humility and quantitative analysis aren't opposites. You can hold both.
@jimmysong recently made a careful argument about BIP110: Bitcoin is a dynamic system, and you can't know a soft fork's consequences in advance. He's right about the uncertainty and the limits of prediction. But there's a third option worth considering.
@jimmysong We don't claim to know whether BIP110 should activate. We claim something narrower: the success-or-failure of a contested fork isn't pure fog. It has structure, and that structure is measurable in advance.