Previously: flightofthefox had completed a full halt-recovery system and was ready to wire validator-shuffling logic into production.
This was a big, busy week. flightofthefox hardened the exact moment shards split and merge — the trickiest part of adaptive sharding — while also building a complete fork-detection and recovery system, overhauling the project's cryptographic foundations, and standing up a live browser demo of the simulation.
125
+108% vs last wk
commits
+11k −2.1k
-5% vs last wk
lines changed
Commits / day
peak 48/day · 7/7 days active
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built
Resharding cut-over, nailed down
The moment a shard splits or merges is the hardest part of adaptive sharding. flightofthefox simplified how each new shard's starting state is derived, fixed committee handoff timing so it flips at the cut not an epoch later, and proved the lifecycle in formal models.
→ see “The Library” on hyperscale.rsForks detected, fenced, and punished
A complete fork-detection system now catches validators who vote for rival blocks, gossips the evidence to the beacon, fences the offending shard until recovery completes, and jails the culprits — replacing soft penalties with key revocation and pool-wide conviction.
→ see “The Overlap” on hyperscale.rsCrypto rebuilt from scratch
flightofthefox created a dedicated crypto interface with separate BLS and mock implementations, routing all signing and verification through clean traits — making the system safer to run and easier to test deterministically.
→ see “The System” on hyperscale.rsThe bottom line
Standout change
The exact moment a shard splits or merges is now derived through a single, tested, formally modeled path — the keystone of adaptive sharding.
What's next
Likely next: completing the validator-shuffling integration into the live system, now that shuffle intervals are derived from timing parameters and the beacon's conviction and revocation machinery is in place.
Heard in the chat
The mood: A heated exchange about marketing and communication, plus interest in community testing and a new sharding FAQ comparison page on the website.
“The main issue with the design at the moment is it just slaps byzantine nodes with a wet bus ticket.”
— flightofthefox, in the community Telegram
This week's concept
The Library— The moving day that never happensThe reshape cut-over — the precise instant a shard's state subtree is handed to its children — is the heart of adaptive sharding, and this week it was simplified, tested, and formally modeled end to end.
hyperscale.rs/library Jargon, decoded
Equivocation — When a validator signs conflicting votes for the same round, which is self-proving evidence of dishonesty.
Key revocation — Permanently disabling a validator's identity as punishment for proven cheating, replacing a temporary jail sentence.
Cut-over — The exact moment a shard split or merge takes effect, when committees and state hand off to the new arrangement.
Where the work landed
crypto newtypes, wave registry, transfer manifest consolidation
jailing, conviction tiers, shuffle interval derivation
fork detection, fork fences, equivocation evidence
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 13 · ~month 3 of 4 · 76%. Since day one: 2,527 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-27