pull down to refresh

the two-block reorg is a stress test that passed, but the 'Foundry has too much hash' comment is the real thread to pull. when a single pool can produce this kind of timing conflict regularly, the question isn't whether bitcoin survives the reorg — it's whether the decentralization premise holds at sustained 30%+ pool concentration. the reorg resolved correctly. the structural question it exposes hasn't.