XI'AN · HYPERSCALE FOR RADIX

Hyperscale Weekly

Week #14 · 10–16 Aug 2026 · Milestone 2 · Radix Engine · Week 2 · ~month 1 of 5

Split the work, not the world

MILESTONE 2 PROGRESS9%

Previously: flightofthefox had unified the codebase onto one engine with zero external Radix dependencies and begun wiring the fee system and cross-shard settlement into the new foundation.

This was a big, wide-ranging week. flightofthefox overhauled how transactions prove they're allowed to act, brought post-quantum signatures online, and carefully spelled out exactly what happens to cross-shard transactions when a shard terminates. Milestone 2's Radix Engine feature-parity work is hitting its stride.

206

-16% vs last wk

commits

+21k −5.5k

-17% vs last wk

lines changed

427

files touched

day commit streak

Commits / day

peak 60/day · 6/7 days active

Momentum

Lines changed / week

last 8 weeks

89% Rust8% Config2% Docs

What flightofthefox built

Badges take over from signatures

The VM's authorization model was rebuilt: holding a badge now grants permission where a raw signature used to, and accounts mint a proof they can present later. This brings the Radix Engine's access control to the sharded VM.

→ see “The Journey” on hyperscale.rs

Post-quantum crypto goes live

ML-DSA-65 post-quantum signatures and secp256k1 are now wired through the transaction path, and the address system was rebuilt with protocol-hash-pinned derivations. flightofthefox noted parity with industry post-quantum efforts.

→ see “The System” on hyperscale.rs

The dead shard's will, fully spelled out

Dozens of commits hardened the rules for cross-shard transactions caught when a shard terminates — evidence windows measured in beacon epochs, settled-set serving windows, and boundary records that rebuild accounts a replay never reached.

→ see “The Will” on hyperscale.rs

The bottom line

Standout change

The authorization model now uses badges and proofs instead of raw signatures — a fundamental shift bringing the Radix Engine's access control to the sharded VM.

What's next

Likely next: continuing to port Radix Engine resource types like non-fungible tokens and collections, and wiring the fee system deeper into the now-badge-aware authorization path.

Heard in the chat

The mood: Chat buzzed about AI-powered security auditing and whether binary-field cryptography might change hash-function choices, with flightofthefox reassuring that a hash swap is trivial and red-teaming shou

“it will be a very fun exercise at the first testnet, for everyone to point their favourite frontier models at the code and try to hack their way to king of the hill 😅”

— flightofthefox, in the community Telegram

This week's concept

The Journey— One payment crosses a sharded world

The authorization model is the heart of Milestone 2's Babylon feature-parity goal — badges, proofs, and stored rules are how the Radix Engine controls who can do what, and this week that system took shape on the sharded foundation.

hyperscale.rs/journey

Jargon, decoded

ML-DSA-65 — A post-quantum signature standard approved by NIST, designed to resist future quantum computers.

Badge — A digital credential stored on-chain that grants permission to perform operations, replacing the need for a raw signature each time.

Securify — Upgrading an account so stored logic rules govern its authorization instead of a simple signature check.

Where the work landed

types · The System

address system and signature scheme overhaul

node · The Will

straddler settlement and terminal handoff hardening

vm/manifest-builder · The Journey

transaction building and authorization wiring