HYPERSCALE-RS · THE BUILDER'S LOG

Hyperscale Weekly

第 27 周 · 9–15 Nov 2026
分割工作,而非世界
本周工作
Hardening shard chains so bad timing can never split agreement
Adaptive Sharding54%
Foundations & reliability34%
The new VM11%
Validator tooling & testnet1%

Previously: flightofthefox had the new VM enforcing that contracts can only read cross-shard state that was actually proven and served to them.

After last week's VM work, flightofthefox swung back to the shard machinery itself — the rules that keep dozens of parallel chains in agreement about who's in charge and when. It was a week of tightening certificate rules and rehearsing rare failure days in the simulator, with the VM still ticking along in the background.

20
-89% 对比上周
次提交
+2.1k −722
-88% 对比上周
行代码变更
37
个文件改动
0
天连续提交
每日提交
一
二
三
四
五
六
日
峰值 16/天 · 2/7 天活跃
势头
每周变更行数
最近 8 周
95% Rust5% Config
flightofthefox 构建了什么

Clocks lose their power to certificates

flightofthefox rewrote how nodes accept quorum certificates so a certificate counts by the epoch it was signed for, never by a node's own clock. That removes a whole family of timing-based disagreements before they can fork a chain.

→ 在 hyperscale.rs 查看“The Clock”

A taller fence against forks

The chain's 'highest certified block' now only rises through a strict gate — refusing halted certificates, capping restarts, and holding a certificate until its own committee's window opens. A restart can no longer drag agreement backwards.

→ 在 hyperscale.rs 查看“The Overlap”

Rehearsing the rarest days, faster

Fast simulations now guard the shard-split message packing and data-fetching rules, and a pending fork scenario can find its rebuilt host by placement. Rare disasters are cheaper to deliberately rehearse.

→ 在 hyperscale.rs 查看“The Crash Lab”
本周要点
最亮眼的变化
Certificates are now judged purely by the epoch they were signed for, so a lying or drifting clock can no longer change what counts as agreed.
接下来做什么
Likely next: finishing the fetch-grace and sync floors around adopted certificates, plus more simulator coverage for the fork scenarios.
聊天室见闻

氛围:Mostly morning greetings and jokes; one member asked when a beta version of hyperscale.rs is coming.

“whoever invented quantum computers is the worst. why can’t we just have nice things like BLS”
— flightofthefox,来自社区 Telegram
本周概念
The Clock— A clock made of votes
The biggest share of the week went into making epoch-signed facts — not local time — decide which certificates count, so every honest node derives the same answer from the same evidence.
hyperscale.rs/clock
术语解读
High QC — The latest quorum-signed certificate a node keeps as its high-water mark of agreed history.
Halt bridge — The rule that decides when a chain's stop counts, judged by the epoch it was signed in.
工作落在了哪里
certificate acceptance rules reworked
high-QC gate and restart floors
fast sims guarding split and sync rules
参考 — 概念地图、路线图与链接▾
全景图
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.
四个部分
54%
Adaptive Sharding
Shards that split and merge on their own · Aug 2026
11%
The new VM
A new engine built from scratch so smart contracts run across shards
–
Indexing & APIs
So wallets and apps can read a sharded network
1%
Validator tooling & testnet
Running a node, and a public test network
34%
Foundations & reliability
Networking, storage, crypto and testing that every part stands on
条形表示本周改动行数的占比。共享的底层工作计入 Foundations & reliability。 自第一天以来:6,138 次提交 — 一位开发者,完全公开进行。
链接
由 AI 根据公开提交、社区聊天和 hyperscale.rs 撰写 — 可能存在错误。 · 生成于 2026-11-16
Hyperscale Weekly — 第 27 周 · 9–15 Nov 2026