Previously: flightofthefox had rebuilt cross-shard verdicts and the beacon fold, and was expected to continue the verdict, claims and signer plumbing.
This week flightofthefox stepped back from the engine internals and gave the network a new set of pipes, ripping out one transport entirely and standardising on another, plus DNS-based discovery. Meanwhile the crash-recovery drills moved onto the production harness, and staking pools learned several new tricks.
+4.2k −10k
-30% vs last wk
lines changed
Commits / day
peak 31/day · 6/7 days active
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built
One network backend, fully swapped
flightofthefox removed the old libp2p transport completely and finished moving everything to iroh, with relays helping nodes connect and DNS records naming a network's peers. Simpler networking means validators are easier to run and connect.
→ see “The Triage” on hyperscale.rsRestart drills go live-fire
The crash-recovery scenarios that were proven in the simulator now also run against the real production build, covering restarts, crashes and partition stalls. A network that recovers cleanly from restarts is one the community can safely run.
→ see “The Crash Lab” on hyperscale.rsTime gets simpler and stricter
Chain timestamps are now plain Unix time, transactions whose validity window can't be reached are refused, and epochs shorter than two consensus views are banned. Fewer conversions means fewer places for clock bugs to hide.
→ see “The Clock” on hyperscale.rsStaking pools get real powers
Pools can now found themselves with stake and registration in one step, open on any deposit, hand over ownership, and build their own unjail path. This is validator on-ramp plumbing taking shape ahead of testnet.
→ see “The Governor” on hyperscale.rsAlso this week
- A transaction can now be published to its shards from a host seated nowhere.
- Beacon now publishes each shard's rotation order and the next shuffle boundary.
- Nodes keep an hour of certified header summaries per shard.
- A cross-shard spend beside a pending leg is now sent to its whole committee.
- A node can be started from a network file alone, from the library.
The bottom line
Standout change
The old libp2p networking transport was removed entirely, making iroh the one and only way Hyperscale nodes talk to each other.
What's next
Likely next: continuing the staking-pool and validator onboarding plumbing, plus the hinted 'more optimized' network design he teased for the coming months.
Heard in the chat
The mood: Chat was dominated by the Binance hack and DAO finance gripes; flightofthefox hosted a Friday voice call and promised to improve his mic.
“happy friday all ... seems like everyone's gone to the rapture”
— flightofthefox, in the community Telegram
flightofthefox explained
Networking is separate from sharding
He explained that networking is orthogonal to sharding — relays just help nodes connect — and hinted at a larger, more optimized network design in the next couple of months.
AI coding tools
He finds AI workflows useful for auditing and review work, but not for implementation because they're too opaque and harder to course-correct.
This week's concept
The Triage— The critical never queues behind the bulkThe biggest change of the week was the network layer: libp2p is gone, iroh is the only backend, and peers can now find each other through DNS — a full re-plumbing of how nodes talk.
hyperscale.rs/triage Jargon, decoded
Relay — A helper node that passes traffic between validators that can't connect directly.
Unix time — The standard worldwide count of seconds since 1970, used as the chain's clock.
libp2p — The previous networking library for peer-to-peer connections, now removed.
Where the work landed
node startup, handles and hosting reworked
restart and crash scenarios on production
old transport fully removed
queries, watch channel, schedule publication
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 13 · since August 2026. Since day one: 5,717 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-11-02