XI'AN · HYPERSCALE FOR RADIX

Hyperscale Weekly

Неделя №11 · 20–26 Jul 2026 · Milestone 1 · Adaptive Sharding · Week 13 · ~month 3 of 4

Раздели работу, а не мир

ПРОГРЕСС ЭТАПА 176%

Previously: flightofthefox had completed a full halt-recovery system and was ready to wire validator-shuffling logic into production.

This was a big, busy week. flightofthefox hardened the exact moment shards split and merge — the trickiest part of adaptive sharding — while also building a complete fork-detection and recovery system, overhauling the project's cryptographic foundations, and standing up a live browser demo of the simulation.

125

+108% к прошлой неделе

коммитов

+11k −2.1k

-5% к прошлой неделе

строк изменено

300

файлов затронуто

34+

дней подряд с коммитами

Коммиты / день

пик 48/день · 7/7 активных дней

Динамика

Строк изменено / неделя

последние 8 нед.

93% Rust7% Config

Что построил flightofthefox

Resharding cut-over, nailed down

The moment a shard splits or merges is the hardest part of adaptive sharding. flightofthefox simplified how each new shard's starting state is derived, fixed committee handoff timing so it flips at the cut not an epoch later, and proved the lifecycle in formal models.

→ смотрите «The Library» на hyperscale.rs

Forks detected, fenced, and punished

A complete fork-detection system now catches validators who vote for rival blocks, gossips the evidence to the beacon, fences the offending shard until recovery completes, and jails the culprits — replacing soft penalties with key revocation and pool-wide conviction.

→ смотрите «The Overlap» на hyperscale.rs

Crypto rebuilt from scratch

flightofthefox created a dedicated crypto interface with separate BLS and mock implementations, routing all signing and verification through clean traits — making the system safer to run and easier to test deterministically.

→ смотрите «The System» на hyperscale.rs

Главное

Главное изменение

The exact moment a shard splits or merges is now derived through a single, tested, formally modeled path — the keystone of adaptive sharding.

Что дальше

Likely next: completing the validator-shuffling integration into the live system, now that shuffle intervals are derived from timing parameters and the beacon's conviction and revocation machinery is in place.

Услышано в чате

Настроение: A heated exchange about marketing and communication, plus interest in community testing and a new sharding FAQ comparison page on the website.

“The main issue with the design at the moment is it just slaps byzantine nodes with a wet bus ticket.”

— flightofthefox, в Telegram сообщества

Концепция недели

The Library— The moving day that never happens

The reshape cut-over — the precise instant a shard's state subtree is handed to its children — is the heart of adaptive sharding, and this week it was simplified, tested, and formally modeled end to end.

hyperscale.rs/library

Жаргон — простыми словами

Equivocation — When a validator signs conflicting votes for the same round, which is self-proving evidence of dishonesty.

Key revocation — Permanently disabling a validator's identity as punishment for proven cheating, replacing a temporary jail sentence.

Cut-over — The exact moment a shard split or merge takes effect, when committees and state hand off to the new arrangement.

Куда легла работа

types · The System

crypto newtypes, wave registry, transfer manifest consolidation

beacon · The Lottery

jailing, conviction tiers, shuffle interval derivation

shard · The Overlap

fork detection, fork fences, equivocation evidence