Previously: flightofthefox was in week 2 of Milestone 2, overhauling the authorization model to use badges and proofs, adding post-quantum signatures, and hardening cross-shard straddler rules.
Week 3 of Milestone 2 was a deep dive into the virtual machine's bones. flightofthefox rebuilt how the VM describes and stores component state, how resources like tokens identify themselves, and how nodes fetch records from each other across shards — all while musing about a privacy future for the network.
409
+66% vs last wk
commits
+31k −11k
+46% vs last wk
lines changed
Commits / day
peak 74/day · 7/7 days active
Momentum
Lines changed / week
last 8 weeks
83% Rust15% Config1% Docs
What flightofthefox built
The VM learns to describe itself
flightofthefox gave the VM a formal vocabulary for component layouts, field sizes, and event payloads — so the engine can read and refuse malformed data before it ever runs, making smart contracts safer by construction.
→ see “The Crash Lab” on hyperscale.rsResources find their own addresses
Tokens and other resources now derive their identity from the issuer that created them rather than an external label, making ownership and minting rules self-consistent and tamper-resistant across every shard.
→ see “The Library” on hyperscale.rsEach node fetches its own truth
Nodes now pull component records from the shard that sealed them instead of keeping a global copy, and each simulated node gets its own engine world — a major step toward realistic multi-shard testing.
→ see “The Journey” on hyperscale.rsThe bottom line
Standout change
The VM can now formally describe and validate its own component layouts, event payloads, and resource identities — turning runtime crashes into compile-time refusals.
What's next
Likely next: continuing to wire resource behaviors (minting, burning, collections) into the newly shaped VM, and pushing the per-node derivation path deeper into cross-shard record fetching.
Heard in the chat
The mood: A lively week — flightofthefox floated the idea of optional privacy (Zcash-style shielding) built natively into the sharded VM, sparking debate about regulation and whether Radix itself should be shie
“what if the best sharded blockchain, can also be the best privacy blockchain”
— flightofthefox, in the community Telegram
This week's concept
The Crash Lab— Rehearsing the rarest dayMost of the week was about making the VM self-describing — giving every record, field, and event a formal shape the engine checks — which is the foundation for deterministic, replayable multi-shard testing.
hyperscale.rs/crashlab Jargon, decoded
Seal — A cryptographic stamp that proves a component or resource was created by the right authority.
Cell — A storage slot in the VM that holds a piece of a component's state, like a field in a record.
Wasmtime — The engine that actually runs compiled smart contracts; flightofthefox upgraded it to the latest version.
Where the work landed
VM shape descriptions and record layout overhaul
Per-node engine worlds and fuzz lane rebuild
Cross-shard record fetching and derivation
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 3 · ~month 1 of 5 · 14%. Since day one: 3,623 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-24