XI'AN · HYPERSCALE FOR RADIX

Hyperscale Weekly

Week #3 · 25–31 May 2026 · Milestone 1 · Adaptive Sharding · Week 5 · ~month 1 of 4

Split the work, not the world

MILESTONE 1 PROGRESS29%

Previously: flightofthefox had scaffolded the beacon crate — the slow coordination chain that will track validators and the shard map — and reshaped the production node around a thread-per-shard model, with The Crash Lab and The Pr

This was a turning-point week. flightofthefox pushed a compiler-enforced safety system across the entire codebase, so unverified blocks or votes literally cannot be used by accident. He also fully wired the beacon into the production node and replaced an older recovery path with a cleaner skip flow.

184

-27% vs last wk

commits

+15k −11k

+22% vs last wk

lines changed

297

files touched

day commit streak

Commits / day

peak 45/day · 7/7 days active

Momentum

Lines changed / week

last 8 weeks

96% Rust4% Config

What flightofthefox built

Compiler-enforced safety everywhere

A new typestate wrapper now forces the compiler to reject any code that tries to use a block, vote, or certificate before it has been cryptographically checked. Unverified data can no longer slip through by accident — a deep structural safety win for The Overlap.

→ see “The Overlap” on hyperscale.rs

The beacon wakes up

The beacon was fully plugged into the production node: sync, gossip, fetch pools, timers, and the SPC state machine all came online. An older 'recovery' path was retired in favour of a simpler skip flow for missed blocks.

→ see “The Census” on hyperscale.rs

The Crash Lab grows teeth

The simulator absorbed multi-coordinator, Byzantine, and topology-change scenarios, plus cross-network signature rejection tests, so a wider range of attacks can now be replayed byte-for-byte in The Crash Lab.

→ see “The Crash Lab” on hyperscale.rs

The bottom line

Standout change

A compiler-enforced 'verified' wrapper now covers nearly every consensus type, making it structurally impossible to trust an unverified block, vote, or certificate.

What's next

Likely next: driving a full beacon epoch transition end-to-end through the simulator, including the new skip flow.

Heard in the chat

The mood: Quiet week in chat — flightofthefox heads-down on the codebase.

This week's concept

The Overlap— Provably fork-free

Nearly every consensus type now has to be cryptographically verified before the compiler will let the code touch it, making it structurally impossible for unverified data to influence a decision. This is fork-safety baked into the type system.

hyperscale.rs/overlap

Jargon, decoded

Typestate — A coding pattern where the type itself records whether a step has happened, so the compiler refuses to let you use something before that ste

Gossip — The way nodes spread messages peer-to-peer, each one passing the news to a few neighbours who pass it on, like a rumour.

Unicast — Sending a message to one specific node, the opposite of broadcasting to everyone.

Where the work landed

types · The Overlap

typestate wrappers for verified consensus types

beacon · The Census

wired into node, sync, fetch, skip flow

node

BeaconCoordinator wired into the runner

Reference — concept map, roadmap & links▾

The full picture

The System