XI'AN · HYPERSCALE FOR RADIX

Hyperscale Weekly

第 20 周 · 2026年9月21–27日 · Milestone 2 · Radix Engine · 第8周 · 自2026年8月起
分割工作,而非世界
当前里程碑
Milestone 2 · Radix Engine
移植 Radix Engine,使 Scrypto 能够跨 shard 运行
第8周 · 自2026年8月起

上期回顾:flightofthefox 将费用和资源定价系统端到端打通,并统一了 intent 模型,向 Milestone 2 的 VM 工作深入推进。

Milestone 2 的第8周对 VM 内部跨 shard 交易的跟踪与解析方式进行了深入而专注的重构。flightofthefox 重新设计了整个

32
-92% 对比上周
次提交
+3.1k −3.4k
-76% 对比上周
行代码变更
128
个文件改动
28
天连续提交
每日提交
一
二
三
四
五
六
日
峰值 10/天 · 7/7 天活跃
势头
每周变更行数
最近 8 周
88% Rust7% Config5% Docs
flightofthefox 构建了什么

Cross-shard crossings rebuilt

Most of the week redesigned 'crossings' — how the VM tracks cross-shard transactions end to end. Crossings are now named once with all keys derived from that name, answers carry two verdicts, and blocks carry crossing records directly.

→ 在 hyperscale.rs 查看“The Generals”

Fee holds and vault deposits

Fee reservations are now treated as committed holds inside the kernel, and vault deposits moved from scattered jobs into a single kernel path — making resource handling cleaner and more predictable.

→ 在 hyperscale.rs 查看“The Journey”

Dead execution paths pruned

Several outdated job types and a crossing tombstone mechanism were removed entirely, replaced by simpler flag-based logic — less code to maintain, fewer edge cases to break.

→ 在 hyperscale.rs 查看“The System”
本周要点
最亮眼的变化
The crossing system — how cross-shard transactions are named, tracked, answered, and cleaned up — was comprehensively rebuilt.
接下来做什么
Likely next: continuing to refine the crossing system and tackling the local execution path flightofthefox flagged as a major challenge.
聊天室见闻

氛围:A lively week: a developer named Seböööl dove into the codebase and sparked a detailed exchange about migration, contract compatibility, and whether Babylon and Hyperscale can coexist.

“leg local execution is my vietnam”
— flightofthefox,来自社区 Telegram
flightofthefox 的解释
Migration path to Hyperscale
The rough plan is dump, transform, genesis — contracts rebuilt before launch if devs are active, stragglers upgraded later through beacon-chain voting with blueprints sitting disabled until then.
Component interaction design
Calls between components should work if the target is in immutable config or passed as an argument, but he wants to explore extending the manifest DAG at the call site rather than replicating Radix Engine's method dispatch.
Contract upgrades without proxies
He plans a native blueprint upgrade system so developers don't have to build proxy patterns, with upgrades coordinated through beacon-chain witnesses to apply consistently at the same epoch.
Why no public backlog
The foundation is still in flux, so maintaining a formal spec would slow things down — there is an order of operations, and it's too early to size the migration.
本周概念
The Generals— The two generals put down their messengers
The dominant work this week was rebuilding how cross-shard transactions are tracked and resolved — the core of atomic cross-shard commitment.
hyperscale.rs/generals
术语解读
Crossing — The VM's name for a cross-shard transaction's tracked lifecycle as state moves between shards.
Fee hold — The portion of a transaction's fee reserved upfront before it runs, so it cannot overspend.
Tombstone — A marker showing a cross-shard record has been retired and is safe to clean up later.
工作落在了哪里
vm/effects · The Generals
crossing answers and state effects reworked
vm/kernel · The Generals
vault deposits, fee holds, crossing jobs
APIs updated for new crossing and fee model
参考 — 概念地图、路线图与链接▾
全景图
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 — 第8周 · 自2026年8月起。 自第一天以来:4,959 次提交 — 一位开发者,完全公开进行。
链接
由 AI 根据公开提交、社区聊天和 hyperscale.rs 撰写 — 可能存在错误。 · 生成于 2026-09-28