BLOCKCHAIN & WEB3 FUNDAMENTALS - Chapter 6, Exercise 3 Solution ========================================================== Why the DAO Fork Tests, Rather Than Confirms, Immutability PROBLEM ------- Using this chapter's own account of the DAO hack, explain why the resulting hard fork is described as testing, rather than simply confirming, blockchain's own claimed immutability — connect your answer back to Chapter 3's own tamper-evidence reasoning. SOLUTION -------- Chapter 3 explained why a blockchain's history is tamper-evident: any change to a past block cascades forward, breaking every later block's own recorded link, and an attacker acting alone would have to out-mine the entire honest network to force through an alternate version of history. That's a real, strong guarantee against a lone attacker or small minority secretly rewriting the past. The DAO situation was different in a way that genuinely tests, rather than confirms, that guarantee. The "attacker" who drained roughly $50 million wasn't secretly rewriting old blocks or trying to fake proof-of-work behind the network's back - they exploited a real flaw in the DAO contract's own code, using perfectly normal, valid transactions that the network correctly and honestly processed exactly as written. Nothing about the chain itself was broken or tampered with; the contract's code simply didn't do what its authors intended. The genuinely new question the hard fork raised wasn't "can someone secretly cheat the proof-of-work system" (Chapter 3 and Chapter 4 already cover why that's hard) - it was "if the community broadly agrees a specific, unambiguous outcome was clearly wrong, can enough of them coordinate to voluntarily change the rules going forward and effectively reverse it?" The answer, in this real case, turned out to be yes: a hard fork, chosen and adopted by the majority of the community, exchanges, and miners, did exactly that - producing the ETH chain with the theft reversed, while a minority who rejected the fork kept the original, unaltered history as Ethereum Classic. This shows immutability isn't an absolute physical law with no exceptions - it's a strong default that holds as long as nobody with enough coordinated influence chooses to deliberately change course. The DAO fork is the real, documented case where that coordinated choice actually happened, which is exactly why it tests the concept rather than simply reconfirming what Chapter 3 already established about single-attacker tampering. ANSWER: Chapter 3's tamper-evidence guarantee is about stopping a lone attacker from secretly rewriting history against the network's consent. The DAO fork instead tested whether the community itself, acting with broad, voluntary consent, could deliberately choose to alter the outcome going forward - a genuinely different question, and one Chapter 3's own reasoning doesn't directly answer, which is exactly why the DAO event is treated as a real test of immutability's limits rather than just another example confirming it. ---- WHY THIS WORKS AS AN ANSWER This distinguishes "tamper-evidence against a lone attacker" (Chapter 3's actual guarantee) from "a community's own voluntary, coordinated choice to change the rules" (what actually happened with the DAO fork), showing precisely why the fork is a genuinely new and different scenario rather than a contradiction of anything Chapter 3 claimed.