Fogo: That “resize → late → frozen bank” incident is the whole Fogo thesis in one punch.
On a ~40ms cadence, the chain doesn’t wait for you — it advances. If your validator changes shape, misses timing, and arrives after the bank is already locked, you’re not unlucky… you’re out of spec.
Core point: Fogo is building a network where deterministic execution beats graceful degradation. That makes performance predictable, but it also makes failure predictable: same client assumptions, same hardware expectations, same latency cliffs.
The real question isn’t “can it run fast?” It’s whether Fogo can keep that tight clock without turning geography + infrastructure into the real permissioning layer.