Previously: flightofthefox closed a huge 124-commit week that rebuilt cross-shard verdicts so certificates decide nothing on their own, and took the iroh networking backend to near-production shape.
This week carried that same plumbing forward and spread into new territory: how the beacon's schedule is derived on every host, how signers attach to running shards, and how cross-shard crossing records are retired only on real proof. It's quieter in chat, but the code tells a story of the network's coordination machinery getting tightened from every side.
+13k −7.6k
-47% vs last wk
lines changed
Commits / day
peak 26/day · 6/7 days active
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built
Every host folds the beacon
The beacon coordinator was split so each host runs its own beacon loop and derives the schedule independently — one fold per host, one participant per identity, each block committed exactly once. Fewer ways for nodes to disagree about who's in charge.
→ see “The Census” on hyperscale.rsCrossings retire on proof
A crossing record — the trail a cross-shard transfer leaves behind — now retires only when an attested certificate says the transfer was actually taken, with a floor in the claims section. No more 'probably fine by now'.
→ see “The Generals” on hyperscale.rsOne replica, many signers
Each hosted shard now keeps a single running replica, and validator signers get seated onto it and sign shard and execution artifacts. The validator identity model is now written down in the docs.
→ see “The Overlap” on hyperscale.rsSlow sims get three hours
The simulator gained longer CI budgets, stricter timing rules — a run that stops advancing its clock now fails — and trace updates folded into one step, so rarer bugs get caught before they ship.
→ see “The Crash Lab” on hyperscale.rsAlso this week
- Shards are now cut only once no row of the shard can still hear the cut.
- Halt recovery runs ahead of the committee shuffle and reshape draws.
- Archive nodes now decode and store every committed block, with header copies keyed by digest.
- Block sync only starts on a certificate that actually verifies.
- Store durability is now tracked only in test runs that can lose power.
The bottom line
Standout change
Cross-shard crossing records can now only be retired when an attested certificate proves the transfer was actually taken — closing a trust gap in the claims system.
What's next
Likely next: finishing the beacon fold/participant split and signer seating, then continuing the verdict and claims plumbing across shards.
Heard in the chat
The mood: Mostly spam bots and memes this week; flightofthefox dropped a cheerful 'gm hyperscalers' and a one-liner about the project being a public good.
“hs-rs isn't a business, it's a public good”
— flightofthefox, in the community Telegram
This week's concept
The Generals— The two generals put down their messengersThe week's core thread was cross-shard atomicity: crossing records, claims, and verdicts now live or die strictly on attested, quorum-backed facts rather than a node's word.
hyperscale.rs/generals Jargon, decoded
Replica — A running copy of one shard's code that its assigned validators share and sign on.
Crossing record — The tracking entry left behind when a transaction moves state from one shard to another.
Fold — A single deterministic pass through the beacon's blocks that derives schedules and committees.
Where the work landed
replica and signer seating model
coordinator split into fold and participant
crossing records retire on attested proof
longer CI budgets, stricter timing checks
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
✓ M1
Adaptive Sharding
~4 mo
Now: Milestone 2 · Radix Engine — Week 12 · since August 2026. Since day one: 5,635 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-10-26