XI'AN · HYPERSCALE FOR RADIX

Hyperscale Weekly

Hafta #17 · 31 Aug – 6 Sept 2026 · Milestone 2 · Radix Engine · Week 5 · ~month 1 of 5
İşi böl, dünyayı değil
KİLOMETRE TAŞI 2 İLERLEMESİ23%

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% geçen haftaya göre
commit
+4.1k 711
-80% geçen haftaya göre
değişen satır
93
dokunulan dosya
0
günlük commit serisi
Commit / gün
P
S
Ç
P
C
C
P
zirve 18/gün · 2/7 gün aktif
Momentum
Değişen satır / hafta
son 8 hafta
95% Rust2% Docs2% Specs1% Config
flightofthefox ne inşa etti

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.

→ hyperscale.rs'te “The Library” konseptine bakın

Intents 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.

→ hyperscale.rs'te “The Journey” konseptine bakın
Özetin özeti
Öne çıkan değişiklik
The substate sweep gives the network its first real garbage collection — automatically tracking and removing state that nothing can reach anymore.
Sırada ne var
Likely next: finishing the intent-signing and network-validation paths, and integrating the substate sweep into the shard's execution lifecycle.
Sohbette duyulanlar

Hava: 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, topluluk Telegram'ında
flightofthefox açıkladı
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.
Haftanın konsepti
The LibraryThe moving day that never happens
The bulk of this week built the state tree's cleanup machinery — tracking, indexing, and removing state that nothing can reach anymore.
hyperscale.rs/library
Jargon, çözüldü
NullifierA marker the system uses to track state that should eventually be removed once it's no longer reachable.
Substate sweepThe network's automatic garbage collection: finding and removing state entries that nothing can reach anymore.
Expiry bucketA way of grouping state items by the block height at which they should be cleaned up, so each block processes them efficiently.
Çalışma nereye gitti
storage-rocksdb · The Library
substate sweep and nullifier storage
vm/kernel · The Journey
intent signing and network validation
nullifier and sweep data structures
Referans — konsept haritası, yol haritası ve bağlantılar
Büyük resim
The System
The whole sharded design at a glance.
The Journey
One transaction's trip through the network.
The Clock
Consensus-attested time across independent shards.
The Census
The leaderless beacon of validators, stake and shards.
The Overlap
Why two conflicting blocks can never both commit.
The Generals
All-or-nothing cross-shard commits, computed not voted.
The Archive
Every published byte is preserved or provably expired.
The Library
All state in one merkle tree; a shard is a subtree.
The Will
How in-flight transactions settle when a shard dies.
The Lottery
Random, ever-moving committees; proven cheats are jailed.
The Triage
Under overload, urgent traffic never waits for bulk.
The Governor
Validator entry is re-priced every epoch, like a market.
The Crash Lab
The simulator that replays any failure byte-for-byte.
The Proof
Proving safety with maths, not just tests.
The Asterisks
Every design's trade-offs — including Hyperscale's own.
Mainnet'e giden yol
✓ M1
Adaptive Sharding
~4 mo
M2
Radix Engine
~5 mo
M3
Gateway & API
~3 mo
M4
Validator GUI
~3 mo
M5
Migration
~3 mo
M6
Live support
12 mo
Şimdi: Milestone 2 · Radix Engine — Week 5 · ~month 1 of 5 · %23. İlk günden beri: 4.023 commit — tek geliştirici, tamamen halka açık.
Bağlantılar
Halka açık commit'ler, topluluk sohbeti ve hyperscale.rs kaynaklarından yapay zekâ ile yazıldı — hata içerebilir. · oluşturulma 2026-09-07