Previously: flightofthefox had just folded the simulator and production into one shared test-scenario framework, with a clean reshape orchestrator driving both runners.
Building on last week's test consolidation, flightofthefox turned to safety and uncovered the biggest bug yet — a rare way the beacon could finalise the same epoch two different ways across a network split. He reproduced it in the simulator, closed it with a new pool-ratified commit path, and proved the fix in five new mathematical models. A landmark week for the beacon's trustworthiness.
+11k −6.1k
+16% vs last wk
lines changed
Commits / day
peak 17/day · 7/7 days active
Momentum
Lines changed / week
last 8 weeks
82% Rust7% Config7% Docs5% Specs
What flightofthefox built
Beacon double-commit, found and fixed
flightofthefox reproduced a rare safety bug where the beacon could finalise the same epoch two different ways across a network split, then built a pool-ratified commit path that mutually excludes the old route — closing the door for good.
→ see “The Census” on hyperscale.rsStraddlers and reshapes, more strongly fenced
Transactions caught in a splitting shard can no longer be evicted while a gate still holds them, and the handoff between old and new committees now waits until the successor is actually live.
→ see “The Will” on hyperscale.rsFive new proofs in math
Five new formal models now prove core safety rules in math: straddler settlement, cross-shard atomic commit, shard consensus, the weighted-time clock, and the dual-commit fix itself.
→ see “The Proof” on hyperscale.rsThe bottom line
Standout change
The beacon's rare double-commit safety gap is now closed, mutually excluded, and proven in math.
What's next
Likely next: the lottery-style validator shuffling that's the other big piece of M1 still to land, now with a much firmer beacon underneath it.
This week's concept
The Census— The beacon that tracks validators & topologyThe central event was the beacon's double-commit safety gap being reproduced, fixed with pool ratification, and mathematically proven. That's a major step forward for the chain that tracks validators and topology.
hyperscale.rs/census Jargon, decoded
Pool ratification — A way for validator pools to vote on and approve a beacon block before it counts as final, replacing a less safe older path.
Dual commit — A safety bug where two conflicting versions of the same block could be finalised at the same time across a split network.
Where the work landed
dual-commit gap closed with pool ratification
reproduced the partition bug end-to-end
new ratification and straddler data types
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 10 · ~month 2 of 4 · 59%. 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