XI'AN · HYPERSCALE FOR RADIX

Hyperscale Weekly

Week #10 · 13–19 Jul 2026 · Milestone 1 · Adaptive Sharding · Week 12 · ~month 3 of 4

Split the work, not the world

MILESTONE 1 PROGRESS71%

Previously: flightofthefox expanded formal proofs with Model F covering the full reshape lifecycle, ran adversarial Monte Carlo analysis on validator shuffling, and moved safe-vote and ratification structures to durable

If last week was about proving the reshape math, this week was about making shards survive the worst. flightofthefox built an entire halt-recovery system — the machinery to detect a frozen shard, redraw its committee, and bring it back to life without losing or duplicating a single transaction. It was a big, dense week with 60 commits across nearly every part of the codebase.

+9% vs last wk

commits

+12k −1.8k

-10% vs last wk

lines changed

142

files touched

34+

day commit streak

Commits / day

peak 18/day · 7/7 days active

Momentum

Lines changed / week

last 8 weeks

89% Rust4% Docs4% Specs3% Config

What flightofthefox built

Shards that heal themselves

flightofthefox built a full halt-recovery pipeline: detecting stalled shards, re-drawing their entire committee, bridging consensus over a proven parent, and freezing cross-shard transactions until the shard is safe again.

→ see “The Will” on hyperscale.rs

Beacon punishes silence, rewards recency

The beacon now jails validators who withhold randomness proposals, weights committee re-samples by how recently each validator served, and evicts the longest-tenured member each shuffle — keeping the lottery fair and alive.

→ see “The Lottery” on hyperscale.rs

Randomness by folding, proven by math

Each shard now publishes a per-block randomness reveal that gets folded into the epoch's shared randomness — the seed for committee draws. A new Quint model proves the fold is correct.

→ see “The Proof” on hyperscale.rs

The bottom line

Standout change

A complete halt-recovery system now lets a frozen shard be detected, re-staffed, and restored without losing or duplicating cross-shard transactions.

What's next

Likely next: wiring the validator-shuffling logic into production now that halt recovery and the beacon's committee-management are in place.

Heard in the chat

The mood: Community discussion about visibility on X and the radix.wiki site, plus an off-topic drama that got wiped by mods. flightofthefox clarified consensus naming and stressed the value of combining simula

“Seems like we're having a week every 2 days 😅”

— flightofthefox, in the community Telegram

This week's concept

The Will— The dead shard's will

The heart of this week was giving dead shards a clean path back: detecting the stall, freezing cross-shard work, rebuilding the committee, and ensuring straddlers resolve by the fence — not by luck.

hyperscale.rs/testament

Jargon, decoded

Halt recovery — The process of detecting a frozen shard, assigning it a new committee, and bringing it back online without losing transactions.

Randomness reveal — A value each shard publishes every block that gets blended together to create the unpredictable seed for the next committee draw.

Fence freeze — Pausing all cross-shard transactions involving a halted shard until its fate is settled.

Where the work landed

node · The Will

halt-recovery pipeline and committee rebuild

types · The Will

recovery data structures and fence types

beacon · The Lottery

jailing, recency weighting, committee caps

Reference — concept map, roadmap & links▾

The full picture

The System

The whole sharded design at a glance.