@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. "I don't know the consequences," he wrote, "and neither do you." He's right about the uncertainty and the limits of prediction. But there's a third option worth considering. The choice isn't only between *knowing* an outcome (hubris) and *not knowing* it (watch and learn). For one specific question, will a contested fork succeed, fail, or split the chain? deep uncertainty doesn't mean zero information. You can't predict a dynamic system's full trajectory. But you can bound it. You can map which conditions push a contested fork toward a clean win, which push it toward a sustained split, and where the boundary between them sits. image That's what simulation is for. We ran 2,694 contested-fork scenarios on real bitcoind nodes using Warnet with mining pools, exchanges, and users modeled as the actors BCAP (https://github.com/bitcoin-cap/bcap) defines, each making independent economic decisions to map exactly that boundary. 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. Full methodology and findings at the University of Wyoming Bitcoin Research Institute workshop @Bradley Rettler , July 13–17. Thread to follow. Epistemic humility and quantitative analysis aren't opposites. You can hold both. View quoted note →

Replies (4)

Cody's avatar
Cody 5 days ago
Wow, this is cool! Do you have any headline results from your model for those of us unwilling to run it ourselves?
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. It's different. We'll have to wait and see. They're right that it's different. But "wait and see" isn't the only option. It's not that the past teaches us nothing, we learn plenty from earlier forks. It's that the outcome doesn't transfer directly. We map 2017 onto today, and the mapping breaks: Different hashrate concentration, different custody landscape, different players. @npub1h8nk...rpev and @jimmysong made sharp points: technical people tend to treat user behavior as more predictable. I think that's right. So the goal here isn't to predict how users will act... it's to respond systematically to the fact that we don't know. 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. The assumptions are explicit and on the table, not baked in and hidden. 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, while staying honest about what you don't know. View quoted note →