XI'AN Β· HYPERSCALE FOR RADIX

Hyperscale Weekly

Week #1 Β· 11–17 May 2026 Β· Milestone 1 Β· Adaptive Sharding Β· Week 3
Split the work, not the world
CURRENT MILESTONE
Milestone 1 Β· Adaptive Sharding
Teaching the network to split and merge its shards on its own
Week 3

A quiet opening week for Hyperscale: no code committed and no chat activity captured. The project has just kicked off its 18-month build, and this calm moment is a good chance to look at the road ahead.

0
-100% vs last wk
commits
+0 βˆ’0
-100% vs last wk
lines changed
0
files touched
0
day commit streak
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built

A calm start to the build

flightofthefox's first reporting week closed with no commits and a quiet chat. The M1 work is just getting underway, and the public repository is empty so far.

β†’ see β€œThe System” on hyperscale.rs

The map is already drawn

The project website lays out the full design vocabulary in plain language, giving the community a shared mental model of what M1 will deliver β€” starting with the beacon that tracks validators.

β†’ see β€œThe Census” on hyperscale.rs
The bottom line
Standout change
A quiet first week β€” no code has landed yet, but the project's 18-month build is officially underway.
What's next
Likely next: flightofthefox will start landing the first commits for the beacon β€” the slow chain that tracks validators and the shard map.
This week's concept
The Systemβ€” Split the work, not the world
With no code yet, this week is about the whole design coming into focus β€” the 'split the work, not the world' thesis that M1 will turn into running software.
hyperscale.rs
Jargon, decoded
Shard β€” A slice of the network that processes its own transactions in parallel with the others.
BFT β€” Short for Byzantine Fault Tolerant β€” a way for a group of computers to agree on something even if some of them are dishonest.
Beacon β€” A slow coordination chain that keeps track of who the validators are and how the shards are arranged.
Reference β€” concept map, roadmap & linksβ–Ύ
The full picture
The System
The whole sharded design at a glance.
The Journey
One transaction's trip through the network.
The Clock
Consensus-attested time across independent shards.
The Census
The leaderless beacon of validators, stake and shards.
The Overlap
Why two conflicting blocks can never both commit.
The Generals
All-or-nothing cross-shard commits, computed not voted.
The Archive
Every published byte is preserved or provably expired.
The Library
All state in one merkle tree; a shard is a subtree.
The Will
How in-flight transactions settle when a shard dies.
The Lottery
Random, ever-moving committees; proven cheats are jailed.
The Triage
Under overload, urgent traffic never waits for bulk.
The Governor
Validator entry is re-priced every epoch, like a market.
The Crash Lab
The simulator that replays any failure byte-for-byte.
The Proof
Proving safety with maths, not just tests.
The Asterisks
Every design's trade-offs β€” including Hyperscale's own.
The road to mainnet
M1
Adaptive Sharding
~4 mo
M2
Radix Engine
~5 mo
M3
Gateway & API
~3 mo
M4
Validator GUI
~3 mo
M5
Migration
~3 mo
M6
Live support
12 mo
Now: Milestone 1 Β· Adaptive Sharding β€” Week 3. Since day one: 2,324 commits β€” one developer, fully in public.
Links
Written by AI from public commits, the community chat and hyperscale.rs β€” may contain mistakes. Β· generated 2026-07-09
Hyperscale Weekly β€” Week #1 Β· 11–17 May 2026