What if a Solidity compiler bug silently strips a reentrancy guard?
A latent Solidity optimizer bug silently stripping reentrancy guards is a compiler-supply-chain shock: many audited contracts are simultaneously vulnerable, draining lending pools and depegging assets, with ETH -5.7% leading on systemic-DeFi fear. Conceptually like a Log4Shell for smart contracts — trust in 'audited' code itself breaks. The skeptic's caveat: real-world blast radius depends on how many high-TVL contracts compiled with the affected optimizer settings, which is unknowable ex-ante and likely overstated initially.
Every number ships with its receipt — the odds, the range, the precedents, and a public grade at Reality Check. The statistical machinery that produces it is proprietary.
The butterfly cascade
How this trigger trickles across markets, left → right — the root shock, its first‑order moves, then the ripple effects. Drag any node; tap a market for its real price history.
Resolution timeline — how this probability is moving
Our model's odds (electric blue) over time vs the market's (Polymarket, amber), from the past toward the 0–6 months horizon. Each dot is a real macro event that nudged the probability — green pushed it up, red pushed it down. Tap a dot for the source. Loading the probability audit trail…
What it would mean
If this plays out, it is a mixed shock. A latent Solidity optimizer bug silently strips a reentrancy guard, letting attackers drain major lending pools and depeg pegged assets. The trigger decomposes into signed root‑shocks — Crypto confidence ▼ · Crypto liquidity ▼ — which propagate through our causal graph to the markets below.