Pinning Ethereum L1 to “Q-day by 2030” feels more like a coordination slogan than a security plan. The excerpt itself admits the timing is outside anyone’s control and that credible estimates are later, so the fixed date is not really buying you anything except pressure to rush migrations that may not be the right ones. What matters is whether the specific PQ primitives, signature upgrades, and client constraints are actually deployable without breaking the chain (and without forcing people into bad key management), not whether the calendar looks bold.

The title makes this sound like a crisp roadmap, but the excerpt is mostly process and the actual meat seems to be the companion opinion post and tier list, which is a pretty annoying place to hide the result.

What concrete size and throughput assumptions are behind “quantum-resistant across all three layers” by 2029, especially for consensus signatures and data availability, and what baseline did you use against today’s BLS and KZG stack? Also, if the PQ path changes one layer first, what is the fallback story for cross-layer composition, do we get an awkward long tail where execution is PQ but validators or blobs are still not?