Previously: flightofthefox had wired in make-before-break committee rotation, overhauled the beacon's randomness, and drawn enthusiastic community reaction with a WASM browser demo of the full node.
This week straddled the finish line of Milestone 1 and the opening days of Milestone 2. flightofthefox confirmed adaptive sharding complete, then dove straight into the Radix Engine work — and the first act was a massive cleanup: merging to one engine, dropping the last Radix library dependencies, and reshaping cross-shard settlement around a unified 'tick' model. It was the biggest single week of refactoring yet.
246
+26% vs last wk
commits
+23k −9.4k
-5% vs last wk
lines changed
Commits / day
peak 53/day · 7/7 days active
Momentum
Lines changed / week
last 8 weeks
79% Rust19% Config2% Docs
What flightofthefox built
One engine, no Radix leftovers
flightofthefox merged the two-engine setup into a single engine crate, adopted a new binary encoding called HBOR, and dropped the last external Radix libraries. The codebase now stands on its own feet.
→ see “The System” on hyperscale.rsCross-shard settlement finds its final shape
Dozens of commits unified how cross-shard transaction batches — now called 'ticks' — are certified, settled, and fenced when a shard terminates. The outcome of any payment is decided by content, not by committee identity.
→ see “The Generals” on hyperscale.rsFees and gas budgeting arrive
Transactions now carry a signed gas budget, the network meters work rather than just counting transactions, and fee burns land in each payer's own receipt. This is the fee system the sharded engine needs to run for real.
→ see “The Journey” on hyperscale.rsThe bottom line
Standout change
The codebase now runs on one engine with zero external Radix dependencies — a clean foundation for everything Milestone 2 will build.
What's next
Likely next: pushing deeper into fee-system wiring and porting more Babylon feature parity onto the now-unified engine.
Heard in the chat
The mood: Lively community discussion about hardware requirements — Raspberry Pi nodes, mobile devices, backup connections — plus a deep dive into validator penalties and staking economics.
“i implement impounding, not slashing. I.E. your stake becomes locked for 90 days... it's just stopping a node runner from being able to repeat attacks, without actually slashing their money permanently”
— flightofthefox, in the community Telegram
This week's concept
The System— Split the work, not the worldThe engine consolidation and Radix dependency removal is the foundational Milestone 2 move — everything else this week rides on top of having one clean engine instead of two inherited ones.
hyperscale.rs Jargon, decoded
Tick — A batch of transactions that a shard processes and certifies together — the unit of cross-shard execution.
HBOR — Hyperscale's own binary encoding format, replacing the Radix library's encoding so the codebase has no external dependencies.
Impounding — Locking a misbehaving validator's stake for a set period rather than permanently destroying it — a gentler alternative to slashing.
Where the work landed
engine merge and Radix dependency removal
tick, wave, finalization and settlement
new binary encoding replacing Radix types
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 1 · ~month 1 of 5 · 5%. Since day one: 2,968 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-10