HYPERSCALE-RS · THE BUILDER'S LOG

Hyperscale Weekly

Semana #27 · 9–15 Nov 2026
Divide el trabajo, no el mundo
EL TRABAJO DE LA SEMANA
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% vs semana pasada
commits
+2.1k −722
-88% vs semana pasada
líneas cambiadas
37
archivos tocados
0
días seguidos con commits
Commits / día
L
M
M
J
V
S
D
pico 16/día · 2/7 días activos
Impulso
Líneas cambiadas / semana
últimas 8 semanas
95% Rust5% Config
Lo que construyó 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.

→ ver “The Clock” en hyperscale.rs

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.

→ ver “The Overlap” en hyperscale.rs

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.

→ ver “The Crash Lab” en hyperscale.rs
En resumen
Cambio destacado
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.
Lo que viene
Likely next: finishing the fetch-grace and sync floors around adopted certificates, plus more simulator coverage for the fork scenarios.
Escuchado en el chat

El ánimo: 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, en el Telegram de la comunidad
El concepto de la semana
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
Jerga, descifrada
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.
Dónde aterrizó el trabajo
certificate acceptance rules reworked
high-QC gate and restart floors
fast sims guarding split and sync rules
Referencia — mapa de conceptos, hoja de ruta y enlaces▾
El panorama completo
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.
Las cuatro partes
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
Las barras muestran la parte de líneas cambiadas esta semana. El trabajo de base compartido cuenta como Foundations & reliability. Desde el día uno: 6,138 commits — un solo desarrollador, totalmente en público.
Enlaces
Escrito por IA a partir de commits públicos, el chat de la comunidad y hyperscale.rs — puede contener errores. · generado 2026-11-16