Previously: flightofthefox hardened the VM to reject invalid constructions at build time, formalized vaults and proofs, and was mid-flight on the proof-and-authorization presenting paths.
This week the Radix network suffered a major VM-level exploit, sending shockwaves through the community. flightofthefox stayed focused on the code, building the network's first real garbage-collection system and tightening transaction signing — while being transparent about protecting Hyperscale's runway and sketching how a future migration would work.
19
-95% vs semana pasada
commits
+4.1k −711
-80% vs semana pasada
líneas cambiadas
0
días seguidos con commits
Commits / día
pico 18/día · 2/7 días activos
Impulso
Líneas cambiadas / semana
últimas 8 semanas
95% Rust2% Docs2% Specs1% Config
Lo que construyó flightofthefox
Unreachable state, swept clean
flightofthefox built a garbage-collection system: nullifiers track state that nothing can reach, grouped by expiry buckets so each block retires exactly what's due. The network can now reclaim storage automatically.
→ ver “The Library” en hyperscale.rsIntents declare their network
Transaction intents now carry signed headers naming which network they're for and how long they're valid — stopping cross-network replay and tightening each intent's time window to the narrowest bound.
→ ver “The Journey” en hyperscale.rsEn resumen
Cambio destacado
The substate sweep gives the network its first real garbage collection — automatically tracking and removing state that nothing can reach anymore.
Lo que viene
Likely next: finishing the intent-signing and network-validation paths, and integrating the substate sweep into the shard's execution lifecycle.
Escuchado en el chat
El ánimo: The Radix network hack dominated all conversation, with debate over relaunching vs. migrating and flightofthefox transparently liquidating XRD to protect Hyperscale's runway.
“hard to hyperscale when you're homeress”
— flightofthefox, en el Telegram de la comunidad
flightofthefox explicó
Sharding localizes failures
One shard halting doesn't impact others, so liveness impact is localized. Prolonged outages get noted by the beacon chain, which rotates the whole committee if needed.
Migration to Xi'an
You'd dump Babylon state at a predetermined epoch, transform it, and load it at Xi'an genesis — same as Olympia to Babylon. The tricky bit is contracts need recompilation.
VM design comes first
The absolute number one priority is building an optimal VM perfectly suited to Hyperscale and sharding. Primitives kept from Scrypto are there because the ideas were genuinely good.
Formal verification limits
You verify smaller models in specialized languages, not the full code. It's not a silver bullet, but having invariants written down makes bugs far less likely.
El concepto de la semana
The Library— The moving day that never happensThe bulk of this week built the state tree's cleanup machinery — tracking, indexing, and removing state that nothing can reach anymore.
hyperscale.rs/library Jerga, descifrada
Nullifier — A marker the system uses to track state that should eventually be removed once it's no longer reachable.
Substate sweep — The network's automatic garbage collection: finding and removing state entries that nothing can reach anymore.
Expiry bucket — A way of grouping state items by the block height at which they should be cleaned up, so each block processes them efficiently.
Dónde aterrizó el trabajo
substate sweep and nullifier storage
intent signing and network validation
nullifier and sweep data structures
Referencia — mapa de conceptos, hoja de ruta y enlaces▾
El panorama completo
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.
El camino a mainnet
✓ M1
Adaptive Sharding
~4 mo
Ahora: Milestone 2 · Radix Engine — Week 5 · ~month 1 of 5 · 23%. Desde el día uno: 4,023 commits — un solo desarrollador, totalmente en público.
Enlaces
¿Preguntas? flightofthefox siempre está feliz de conversar en el Telegram de la comunidad.
Escrito por IA a partir de commits públicos, el chat de la comunidad y hyperscale.rs — puede contener errores. · generado 2026-09-07