Previously: flightofthefox had swept the VM for correctness — fee holds, cross-shard lock cycles and co-hosted validator seating.
A big, hands-on week: flightofthefox pushed 124 commits, largely hardening the networking layer behind a new backend and tightening the rules that decide cross-shard results. In chat, he also laid out his full plan for how history and archiving will work in a sharded world.
124
-19% vs last wk
commits
+26k −13k
+74% vs last wk
lines changed
Commits / day
peak 33/day · 6/7 days active
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built
A new network engine matures
flightofthefox spent most of the week on the iroh networking backend: relays for home networks, NAT testbeds, benchmarks against the old backend, and strict budgets on who gets answered. Getting this right means validators can run behind ordinary home internet.
→ see “The Triage” on hyperscale.rsVerdicts, not votes
The rules for cross-shard results were tightened so a certificate alone can never decide an outcome, and every claim a block makes about another shard must be backed by that shard's own signed verdict. This keeps cross-shard transactions honest by construction.
→ see “The Generals” on hyperscale.rsPruning with proof
Old data can now be safely swept away once a block's own frontier allows it, with each deletion merged into one tidy proof. Validators keep less, prove what they kept, and sync faster.
→ see “The Archive” on hyperscale.rsShard boundaries get teeth
Reshapes, terminal records and shard boundaries were fenced off — a shard can't be reshaped while its termination record stands, and rows from before a boundary can't be misread. Fewer ways for splits and merges to go wrong.
→ see “The Will” on hyperscale.rsAlso this week
- A container-based testbed now seats a whole committee across different home-network setups.
- Unused cross-shard data older than a boundary is now provably discardable.
- The gossip layer was rebuilt so a false copy can't block later true copies.
- The iroh probe got a plain-English guide for testing between two home networks.
The bottom line
Standout change
The iroh networking backend is nearly production-ready, including relays and testbeds that prove validators can talk across ordinary home networks.
What's next
Likely next: finishing the verdict/claims plumbing across shards and making the iroh backend the production default.
Heard in the chat
The mood: The chat was dominated by a long, thoughtful discussion on archiving history and how gateways will serve data in a sharded world — plus the usual asking about when a public testnet will land.
“the great old one's ways are unknowable. do not let your mind linger on PR #171, lest you are willing to lose it”
— flightofthefox, in the community Telegram
flightofthefox explained
Archiving in a sharded world
Archive nodes will be a config of the normal client, listening to shard header gossip and batching history into object storage — validators can't carry old data because shuffling them with terabytes of history would break everything.
Permissionlessness has limits
Permissionless doesn't mean the network owes anyone answers — a shard's 128 validators have finite bandwidth, so archivists will likely bond something of value to register as their admission ticket to queries.
Babylon's data weight
Babylon validators carry nearly a terabyte of disk for under 20 GB of actual state — he suspects it was just an MVP that was never improved, not compliance.
Native blueprints can wait
On porting things like Ociswap pools to hs-vm: there are many months of fundamental work before those topics reach the top of the list.
This week's concept
The Generals— The two generals put down their messengersThe week's deepest thread was making cross-shard commitment purely mechanical: outcomes follow from facts already signed on-chain, never from a message someone could forge or misplace.
hyperscale.rs/generals Jargon, decoded
iroh — A modern Rust networking library for connecting nodes, even behind home routers.
NAT — The router technology in home networks that can block direct connections between machines.
Verdict — A shard's signed statement of the outcome of a transaction it executed.
Where the work landed
new network backend hardened and benchmarked
fault gates and scenario wiring configured
cross-shard verdict and claim rules tightened
boundary and terminal-record rules fenced off
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 11 · since August 2026. Since day one: 5,563 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-19