BLOCKCHAIN & WEB3 FUNDAMENTALS - Chapter 4, Exercise 1 Solution ========================================================== What Happens When a Lot of New Mining Power Joins Overnight PROBLEM ------- Explain, using this chapter's own difficulty-adjustment mechanism, what would happen to Bitcoin's real average block time if a huge amount of new mining hardware suddenly joined the network overnight, and why the network wouldn't simply stay stuck producing blocks much faster than 10 minutes forever. SOLUTION -------- In the short term, a sudden, large increase in total mining power would make blocks come in faster than the intended 10-minute average - more machines searching for a valid nonce means a valid one gets found sooner, on average, across the whole network. This wouldn't last, though, because of Bitcoin's own difficulty adjustment mechanism. The network re-targets difficulty every 2016 blocks - it doesn't wait for the full 10-minute-per-block period to elapse in real time; it waits for 2016 actual blocks to be mined, however fast or slow that turns out to take. If a burst of new hardware made those 2016 blocks come in well under the expected 20,160 minutes (14 days), the network detects that when the adjustment point is reached and raises the difficulty target proportionally - making the mining puzzle harder to solve. Once the difficulty is raised to match the new, larger amount of total mining power, the average time to find a valid nonce goes back up toward the intended 10 minutes per block, even though there's now much more hardware working on the problem. The network doesn't need every miner to agree to slow down - the built-in adjustment does this automatically, purely from watching how quickly the previous 2016 blocks were actually mined. ANSWER: Block times would temporarily drop below 10 minutes as more mining power joined, but at the very next 2016-block difficulty adjustment, the network would raise the difficulty target to match, pushing the average block time back toward 10 minutes - the network self-corrects automatically rather than staying permanently faster just because more hardware joined. ---- WHY THIS WORKS AS AN ANSWER This correctly identifies that the adjustment is triggered by a block count (every 2016 blocks), not a fixed real-world time interval, and explains the actual self-correcting mechanism the chapter describes rather than just asserting that "it balances out."