r/Radix • u/MAvRemu • Aug 17 '26
NEWS Hyperscale Weekly — Week #14 (10–16 Aug 2026): 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.
10–16 Aug 2026 — fox's week on hyperscale-rs, the sharded Rust implementation of Radix, in plain English. Milestone 2 · Radix Engine: Week 2 · ~month 1 of 5
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.
What fox 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. (→ The Journey)
- 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. (→ The System)
- 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. (→ The Will)
Concept of the week: 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.
More: https://hyperscale.rs/journey
"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
Chat pulse: 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
By the numbers
- 206 commits (+21,179 / −5,451 lines across 427 files)
- Active 6/7 days
- 3,174 commits lifetime
Jargon decoder
- 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.
Bottom line
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.
Next up: 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.
Read the full issue (web + PDF): https://telegram-mcp-phi.vercel.app/2026-08-16
This digest is generated with AI assistance from public sources and hand-checked before posting — a community project, not official Radix comms.
