BIP 50 — March 2013 Chain Fork Post-Mortem
Gavin Andresen's post-mortem of the March 2013 fork: a block that 0.8 nodes accepted and some pre-0.8 nodes rejected, the Berkeley DB lock limit behind it, and the fixes that followed.
Entries tagged with this topic. Spans across types and sources — explore connections between people, events, and themes.
4 entries / 0 threads
Gavin Andresen's post-mortem of the March 2013 fork: a block that 0.8 nodes accepted and some pre-0.8 nodes rejected, the Berkeley DB lock limit behind it, and the fixes that followed.
Bitcoin Institute ↔ Gavin Andresen, Pieter Wuille, Jeff Garzik, Gregory Maxwell, Luke Dashjr, Marek Palatinus
On March 11, 2013, one large block split Bitcoin: v0.8 nodes accepted it, older nodes rejected it. Developers chose the shorter chain every version accepted, and two pools downgraded to rejoin it.
Jeff Garzik ↔ Satoshi Nakamoto, Gavin Andresen
An integer overflow (CVE-2010-5139) let Block 74638 create 184 billion BTC. Satoshi released a fix 5h 40m after discovery; the fixed chain overtook the bad one about 15 hours after the block.
Bitcoin Institute ↔ Satoshi Nakamoto, Jeff Garzik, Gavin Andresen, knightmb
How the 2010-08-15 overflow incident unfolded: the soft-fork rescue, why a 5-hour response was possible only then, what the transactions themselves show, and the centralization paradox.