XI'AN · HYPERSCALE FOR RADIX

Hyperscale Weekly

第 21 周 · 28 Sept – 4 Oct 2026 · Milestone 2 · Radix Engine · Week 9 · since August 2026
分割工作,而非世界
当前里程碑
Milestone 2 · Radix Engine
Porting the Radix Engine so Scrypto runs across shards
Week 9 · since August 2026

Previously: flightofthefox comprehensively rebuilt the crossing system for tracking cross-shard transactions, and flagged local execution as a major upcoming challenge.

This week, flightofthefox turned from last week's crossing-system rebuild toward a different kind of hard problem: what happens when a shard forks, halts, or needs a new validator seated mid-flight. The commits tell a story of making recovery and validator seating work cleanly on running shards — both in production and in the simulator.

19
-89% 对比上周
次提交
+4.0k −1.1k
-84% 对比上周
行代码变更
64
个文件改动
0
天连续提交
每日提交
一
二
三
四
五
六
日
峰值 19/天 · 1/7 天活跃
势头
每周变更行数
最近 8 周
98% Rust2% Config
flightofthefox 构建了什么

Rebuilding forked shards from anchors

flightofthefox made forked production and simulator shards rebuild themselves from a known anchor point before validators are seated, ensuring recovery always starts from verified state rather than untrusted data.

→ 在 hyperscale.rs 查看“The Archive”

Seating validators on live shards

New validators can now join a running shard once their local store is settled, and co-hosted validators can be seated and released on both production and sim shards — the machinery for the trickle rotation that keeps committees honest.

→ 在 hyperscale.rs 查看“The Lottery”

Halt recovery gets robust

Recovery bindings are now resolved from bounded history rather than pending records, halting shards freeze by withholding validators instead of cutting hosts, and the recovery floor is set before discarding old frontier data.

→ 在 hyperscale.rs 查看“The Overlap”
本周要点
最亮眼的变化
Validators can now be seated into and released from running shards — the live machinery for committee rotation.
接下来做什么
Likely next: continuing to harden halt recovery and connect the validator-seating path to the trickle rotation system.
聊天室见闻

氛围:The chat was dominated by a heated debate about whether XRD holders benefit from Hyperscale, with flightofthefox firmly declining to promise anything beyond the tech.

“what XRD does is not up to me. i'm just building tech, if radix wants to give a grant because it helps achieve their goals than great. this is a good alignment of incentives”
— flightofthefox,来自社区 Telegram
flightofthefox 的解释
DePIN on Hyperscale
DePIN doesn't pose technical challenges — the on-chain part is usually a tiny fraction of the architecture, and the smart contracts platform itself is a sufficient framework.
Token for DePIN rewards
You're better off with discrete tokens for pure-play services rather than muddying up tokenomics that exist to fulfill concrete security goals.
His role vs XRD price
He builds technology and can't solve every problem; whether XRD benefits is outside his domain, though he works hard to be competitive with the market.
Keeping the channel open
Without Radix there'd be no Telegram channel; he keeps it open to share enthusiasm for consensus and answer questions, because Radix people care about this stuff.
本周概念
The Lottery— A jury you can't bribe
Seating and releasing co-hosted validators on running shards is the practical foundation for trickle rotation — the one-seat-at-a-time committee change that disperses corruption while keeping shards live.
hyperscale.rs/kleroterion
术语解读
Anchor — A known-good checkpoint in a shard's history that recovery can safely rebuild from.
Co-hosted validator — Multiple validator identities running on the same physical machine, which is how vnodes work.
Frontier — The leading edge of a shard's chain that recovery must preserve before discarding.
工作落在了哪里
validator seating and release on running shards
production · The Archive
forked shard rebuild from anchors before seating
simulation · The Crash Lab
halt recovery sims on co-hosted layouts
参考 — 概念地图、路线图与链接▾
全景图
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.
通往主网之路
✓ 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
当前:Milestone 2 · Radix Engine — Week 9 · since August 2026。 自第一天以来:5,133 次提交 — 一位开发者,完全公开进行。
链接
由 AI 根据公开提交、社区聊天和 hyperscale.rs 撰写 — 可能存在错误。 · 生成于 2026-10-05