Previously: flightofthefox had wrapped nearly every consensus type in a compiler-enforced 'verified' tag and wired the beacon into the node end-to-end.
This week flightofthefox pushed the verified-tag discipline all the way down into storage and reproduced a real shard-consensus fork in the simulator — then closed it. A timestamp-driven topology schedule now answers 'who's in charge right now' for any moment.
+5.4k −2.8k
-68% vs last wk
lines changed
Commits / day
peak 18/day · 7/7 days active
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built
Storage learns to speak verified
Reads and writes on both shard and beacon storage now return 'verified' blocks — the typestate net from last week tightened so nothing unproven can sneak through persistence. This makes the safety rules structural, not just procedural.
→ see “The Overlap” on hyperscale.rsThe clock becomes queryable
A new per-epoch topology schedule lets any node ask which validators run shard X at time T and get the same answer everywhere. Shard IDs became prefix paths, and committees are computed one epoch ahead — the 'three engines, one clock' idea made real.
→ see “The Clock” on hyperscale.rsShard consensus locks into HotStuff-2
flightofthefox reproduced a conflicting-commit fork caused by an old vote-unlock rule, then closed it with the HotStuff-2 safe-vote rule. Rounds now increase per block, parent hashes are signed, and a timeout pacemaker keeps validators in sync.
→ see “The Overlap” on hyperscale.rsThe bottom line
Standout change
A conflicting-commit fork that could have hit real shards is now reproduced in the simulator and shut down by the HotStuff-2 safe-vote rule.
What's next
Likely next: driving a full epoch transition — with the new topology schedule and HotStuff-2 rule — through The Crash Lab end-to-end.
This week's concept
The Clock— Three engines, one clockThe new timestamp-queryable topology schedule is the architectural centerpiece of the week — it's the concrete lookup table that makes 'three engines, one clock' work for every honest node, every time.
hyperscale.rs/clock Jargon, decoded
HotStuff-2 — A two-round voting rule that makes it mathematically impossible for honest validators to commit conflicting blocks.
Pacemaker — A timer inside the consensus engine that nudges all validators to move on to the next round if no block appears in time.
Where the work landed
typestate wrappers ripple through dozens of files
overflow guards and duplicate-committee rejection
HotStuff-2 safe-vote rule and timeout pacemaker
Reference — concept map, roadmap & links▾
The full picture
The ClockConsensus-attested time across independent shards.
The CensusThe leaderless beacon of validators, stake and shards.
The OverlapWhy two conflicting blocks can never both commit.
The GeneralsAll-or-nothing cross-shard commits, computed not voted.
The ArchiveEvery published byte is preserved or provably expired.
The LibraryAll state in one merkle tree; a shard is a subtree.
The WillHow in-flight transactions settle when a shard dies.
The LotteryRandom, ever-moving committees; proven cheats are jailed.
The TriageUnder overload, urgent traffic never waits for bulk.
The GovernorValidator entry is re-priced every epoch, like a market.
The Crash LabThe simulator that replays any failure byte-for-byte.
The ProofProving safety with maths, not just tests.
The AsterisksEvery design's trade-offs — including Hyperscale's own.
The road to mainnet
Now: Milestone 1 · Adaptive Sharding — Week 6 · ~month 1 of 4 · 35%. Since day one: 2,324 commits — one developer, fully in public.
Links
Questions? flightofthefox is always happy to discuss in the community Telegram.
Written by AI from public commits, the community chat and hyperscale.rs — may contain mistakes. · generated 2026-07-09