Previously: flightofthefox had reshaped the VM's internals — formal component layouts, resource identity, and per-node shard record fetching — pushing toward feature parity with Babylon.
This was a week of deep, grinding VM hardening: flightofthefox made the Radix Engine refuse invalid constructions at every seam, formalized how vaults and resources are described, and restructured large swaths of code into cleaner modules. In the community, a lively discussion about formal verification and privacy showed just how much the project's testing-first philosophy resonates.
349
-21% vs last wk
commits
+17k −6.9k
-44% vs last wk
lines changed
Commits / day
peak 134/day · 5/7 days active
Momentum
Lines changed / week
last 8 weeks
79% Rust18% Config1% Docs1% Specs
What flightofthefox built
The VM learns to say no
Dozens of commits make the engine reject bad inputs — duplicate fields, half-applied supply changes, invalid shapes — at build time instead of crashing at runtime, making the whole system safer by construction.
→ see “The System” on hyperscale.rsVaults and resources take form
Vaults are now named state fields with explicit mint-burn pairs, supply changes must apply whole or not at all, and token denominations are pinned to their resources — giving the token system a precise, checkable structure.
→ see “The System” on hyperscale.rsProofs get provenance and structure
Authority proofs now carry traceable provenance, threshold sign-in gets a formal presenting path, and badge-gating ties to protocol-level evidence — making access control verifiable rather than assumed.
→ see “The Journey” on hyperscale.rsThe bottom line
Standout change
The Radix Engine now rejects an enormous range of invalid constructions — bad shapes, duplicate fields, half-applied token changes — before code ever runs, making smart-contract failures a build-time problem rather than a runtime crash.
What's next
Likely next: continuing to wire resource operations like minting, burning, and vault movements into the hardened VM, and finishing the proof-and-authorization presenting paths that are clearly mid-flight.
Heard in the chat
The mood: Chat buzzed about formal verification after a Zcash bug made headlines, with flightofthefox explaining how privacy relays could work and noting he hasn't chased M1 payment admin yet — too busy buildin
“the better integrated robust testing is from the start - the more it unlocks being able to move at ridiculous velocity - and move with confidence”
— flightofthefox, in the community Telegram
This week's concept
The System— Split the work, not the worldNearly every commit this week drilled into the Radix Engine's core architecture — the execution layer that runs every smart contract — hardening its type system, resource model, and authorization against entire classes of failure before they can ever occur.
hyperscale.rs Jargon, decoded
Vault — A named field inside a smart-contract component that holds a specific kind of token, tracking how much of that resource it contains.
Provenance — A record of where a proof of authority came from, so the system can verify that the right person signed off on an action.
Manifest — A blueprint file that describes what a smart-contract package contains and how it should be published to the network.
Where the work landed
63 files: resource-operation refusals and validation
52 files: manifest builder and construction-time projections
38 files: test consolidation and in-repo guest scaffold
Reference — concept map, roadmap & links▾
The full picture
The ClockConsensus-attested time across independent shards.
The CensusThe leaderless beacon of validators, stake and shards.
The OverlapWhy two conflicting blocks can never both commit.
The GeneralsAll-or-nothing cross-shard commits, computed not voted.
The ArchiveEvery published byte is preserved or provably expired.
The LibraryAll state in one merkle tree; a shard is a subtree.
The WillHow in-flight transactions settle when a shard dies.
The LotteryRandom, ever-moving committees; proven cheats are jailed.
The TriageUnder overload, urgent traffic never waits for bulk.
The GovernorValidator entry is re-priced every epoch, like a market.
The Crash LabThe simulator that replays any failure byte-for-byte.
The ProofProving safety with maths, not just tests.
The AsterisksEvery design's trade-offs — including Hyperscale's own.
The road to mainnet
✓ M1
Adaptive Sharding
~4 mo
Now: Milestone 2 · Radix Engine — Week 4 · ~month 1 of 5 · 18%. Since day one: 4,003 commits — one developer, fully in public.
Links
Questions? 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-08-31