Previously: flightofthefox had completed the cut-over system for shard splits and merges, plus a full fork-detection and jailing pipeline, with validator-shuffling integration flagged as the clear next frontier.
This week flightofthefox delivered on that promise: committee rotation — the one-seat-at-a-time shuffling that keeps shards live — landed as a full make-before-break system wired into the beacon. He also rebuilt how the beacon produces its randomness and validates witness records, and topped it off with a stunning browser demo running the entire node in a tab.
+9.8k −2.9k
-4% vs last wk
lines changed
Commits / day
peak 38/day · 4/7 days active
Momentum
Lines changed / week
last 8 weeks
88% Rust6% Config3% Docs3% Specs
What flightofthefox built
Committee shuffling goes live
flightofthefox built the full make-before-break rotation: committees rotate one seat at a time, capped by sync headroom, so shards never lose quorum mid-shuffle. Merges cancel pending rotations, keeping topology changes safe.
→ see “The Lottery” on hyperscale.rsBeacon randomness, rebuilt
A per-epoch randomness reveal chain now folds into beacon randomness, with formal invariants registered and old witness types cleaned up. This is the lottery's fuel — the unpredictable seed that stops anyone rigging committee assignments.
→ see “The Census” on hyperscale.rsThe whole node in a browser
flightofthefox compiled the full node to WASM and ran an eight-node, multi-shard network in a browser tab with simulated latency. The community loved it — a tangible, visual proof that the architecture works.
→ see “The Crash Lab” on hyperscale.rsThe bottom line
Standout change
Committee rotation — the one-seat-at-a-time shuffling at the core of adaptive sharding — is now wired in and running make-before-break.
What's next
Likely next: hardening the shuffle against edge cases like concurrent merges, then pushing the demo toward community-runnable testnet readiness.
Heard in the chat
The mood: Huge excitement around the browser demo; thoughtful Q&A about beacon-chain resilience and cross-shard wave-cert safety from foxylady and others.
“what happens when you compile the whole node to WASM and slap a multi-shard network in a browser tab 😅”
— flightofthefox, in the community Telegram
This week's concept
The Lottery— A jury you can't bribeCommittee rotation is the heart of validator shuffling — the mechanism that disperses corruption one seat at a time while never leaving a shard without enough honest validators to function.
hyperscale.rs/kleroterion Where the work landed
randomness reveal chain and witness proof overhaul
committee rotation and shuffle records added
browser multi-shard simulation with cross-shard visuals
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 14 · ~month 3 of 4 · 82%. Since day one: 2,605 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-08-03