XI'AN · HYPERSCALE FOR RADIX

Hyperscale Weekly

第 4 周 · 6月1日–7日,2026年 · Milestone 1 · Adaptive Sharding · 第6周 · 4个月计划中的第1个月
分割工作,而非世界
里程碑 1 进度35%

此前:flightofthefox 已经将几乎所有共识类型都用编译器强制执行的 'verified' 标签包装起来,并将 beacon 端到端接入了节点。

本周 flightofthefox 将 verified-tag 规范一路下沉到了存储层,并在模拟器中复现了一个真实的分片共识分叉——然后修复了它。一个由时间戳驱动的拓扑调度表示在,能够为任意时刻回答

86
-53% 对比上周
次提交
+5.4k 2.8k
-68% 对比上周
行代码变更
283
个文件改动
22
天连续提交
每日提交
峰值 18/天 · 7/7 天活跃
势头
每周变更行数
最近 8 周
100% Rust
flightofthefox 构建了什么

Storage learns to speak verified

Reads and writes on both shard and beacon storage now return 'verified' blocks — the typestate net from last week tightened so nothing unproven can sneak through persistence. This makes the safety rules structural, not just procedural.

→ 在 hyperscale.rs 查看“The Overlap”

The clock becomes queryable

A new per-epoch topology schedule lets any node ask which validators run shard X at time T and get the same answer everywhere. Shard IDs became prefix paths, and committees are computed one epoch ahead — the 'three engines, one clock' idea made real.

→ 在 hyperscale.rs 查看“The Clock”

Shard consensus locks into HotStuff-2

flightofthefox reproduced a conflicting-commit fork caused by an old vote-unlock rule, then closed it with the HotStuff-2 safe-vote rule. Rounds now increase per block, parent hashes are signed, and a timeout pacemaker keeps validators in sync.

→ 在 hyperscale.rs 查看“The Overlap”
本周要点
最亮眼的变化
A conflicting-commit fork that could have hit real shards is now reproduced in the simulator and shut down by the HotStuff-2 safe-vote rule.
接下来做什么
Likely next: driving a full epoch transition — with the new topology schedule and HotStuff-2 rule — through The Crash Lab end-to-end.
本周概念
The ClockThree engines, one clock
The new timestamp-queryable topology schedule is the architectural centerpiece of the week — it's the concrete lookup table that makes 'three engines, one clock' work for every honest node, every time.
hyperscale.rs/clock
术语解读
HotStuff-2A two-round voting rule that makes it mathematically impossible for honest validators to commit conflicting blocks.
PacemakerA timer inside the consensus engine that nudges all validators to move on to the next round if no block appears in time.
工作落在了哪里
typestate wrappers ripple through dozens of files
overflow guards and duplicate-committee rejection
HotStuff-2 safe-vote rule and timeout pacemaker
参考 — 概念地图、路线图与链接
全景图
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 1 · Adaptive Sharding — 第6周 · 4个月计划中的第1个月 · 35%。 自第一天以来:2,324 次提交 — 一位开发者,完全公开进行。
链接
由 AI 根据公开提交、社区聊天和 hyperscale.rs 撰写 — 可能存在错误。 · 生成于 2026-07-09
Hyperscale Weekly — 第 4 周 · 6月1日–7日,2026年