XI'AN · HYPERSCALE FOR RADIX
Hyperscale Weekly
Week #1 · 11–17 May 2026 · Milestone 1 · Adaptive Sharding · Week 3 · ~month 1 of 4
Split the work, not the world
MILESTONE 1 PROGRESS18%
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
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.rsThe 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.rsThe 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.rsJargon, 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
Consistent time across independent shards.
The Census
The registry of validators and shards.
The Overlap
Why the chain can never split in two.
The Generals
All-or-nothing commits across shards.
The Archive
How the network remembers its past.
The Library
All state in one clean, reshardable tree.
The Will
Protects transactions caught in a reshape.
The Lottery
Random validator shuffling, ungameable.
The Triage
Detects and removes bad validators.
The Governor
Auto-prices the stake to run a validator.
The Crash Lab
The simulator that replays any failure.
The Proof
Proving safety with maths, not just tests.
The Asterisks
Trade-offs rivals accept — this avoids.
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 · ~month 1 of 4 · 18%. Since day one: 2,324 commits — one developer, fully in public.
Links
Website
hyperscale.rsCode (public)
github.com/hyperscalers/hyperscale-rsMilestone proposal (PDF)
the Xi'an proposalCommunity (Telegram)
t.me/hyperscale_rsAuthor
flightofthefoxQuestions? 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-07-09