Previously: the simulator and production test suites had just been brought into alignment on epochs and follower pools, and the first end-to-end reshape tests were coming online.
This was a consolidation week. flightofthefox folded the dozens of test scripts scattered across the simulator and the production code into a single shared 'scenarios' framework — one set of stories that runs in both places. On top of that, the machinery that runs shard splits and merges got a new conductor, and a quiet but sweeping cleanup tidied the internal folder layout.
+8.0k −6.6k
+1% vs last wk
lines changed
Commits / day
peak 26/day · 7/7 days active
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built
One test suite, two worlds
flightofthefox migrated the simulator tests, the production end-to-end tests, and the fault tests into one shared scenarios framework. The exact same reshape, straddler, and cross-shard stories now run on both harnesses — one source of truth for 'correct.'
→ see “The Crash Lab” on hyperscale.rsA new conductor for splits and merges
flightofthefox introduced a reshape orchestrator that coordinates a split or merge — who seats the new shard, who watches the old one, who keeps things in sync. Ad-hoc logic replaced with a clean duty machine shared by both runners.
→ see “The Will” on hyperscale.rsStart at one, grow on demand
The genesis startup was simplified: every network now boots from a single shard and grows to its target size under the same code path. Fewer magic knobs, and the simulator and production now share one genesis ceremony.
→ see “The Census” on hyperscale.rsThe bottom line
Standout change
The simulator and production code now run the exact same test scenarios end-to-end — the closest the project has come to one source of truth for what 'correct' means.
What's next
Likely next: harden the remaining fault scenarios in the new framework, then move into the lottery-style validator shuffling that M1 still has to deliver.
This week's concept
The Crash Lab— Replay every bug byte-for-byteFor the first time, the simulator and the live code run the exact same test scenarios — every bug found in one is automatically checked against the other, which is the foundation flightofthefox needs before a public testnet.
hyperscale.rs Jargon, decoded
Scenario — A test written once in a shared format that runs on both the simulator and the real production code.
Orchestrator — A coordinator that walks the network through the ordered steps of a complex operation, like splitting a shard in two.
Where the work landed
sweeping refactor: new orchestrator, folder tidy
tests migrated into shared scenarios
new portable scenario crate scaffolded
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 9 · ~month 2 of 4 · 53%. 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