Previously: flightofthefox comprehensively rebuilt the crossing system for tracking cross-shard transactions, and flagged local execution as a major upcoming challenge.
This week, flightofthefox turned from last week's crossing-system rebuild toward a different kind of hard problem: what happens when a shard forks, halts, or needs a new validator seated mid-flight. The commits tell a story of making recovery and validator seating work cleanly on running shards — both in production and in the simulator.
19
-89% vs semana pasada
commits
+4.0k −1.1k
-84% vs semana pasada
líneas cambiadas
0
días seguidos con commits
Commits / día
pico 19/día · 1/7 días activos
Impulso
Líneas cambiadas / semana
últimas 8 semanas
Lo que construyó flightofthefox
Rebuilding forked shards from anchors
flightofthefox made forked production and simulator shards rebuild themselves from a known anchor point before validators are seated, ensuring recovery always starts from verified state rather than untrusted data.
→ ver “The Archive” en hyperscale.rsSeating validators on live shards
New validators can now join a running shard once their local store is settled, and co-hosted validators can be seated and released on both production and sim shards — the machinery for the trickle rotation that keeps committees honest.
→ ver “The Lottery” en hyperscale.rsHalt recovery gets robust
Recovery bindings are now resolved from bounded history rather than pending records, halting shards freeze by withholding validators instead of cutting hosts, and the recovery floor is set before discarding old frontier data.
→ ver “The Overlap” en hyperscale.rsEn resumen
Cambio destacado
Validators can now be seated into and released from running shards — the live machinery for committee rotation.
Lo que viene
Likely next: continuing to harden halt recovery and connect the validator-seating path to the trickle rotation system.
Escuchado en el chat
El ánimo: The chat was dominated by a heated debate about whether XRD holders benefit from Hyperscale, with flightofthefox firmly declining to promise anything beyond the tech.
“what XRD does is not up to me. i'm just building tech, if radix wants to give a grant because it helps achieve their goals than great. this is a good alignment of incentives”
— flightofthefox, en el Telegram de la comunidad
flightofthefox explicó
DePIN on Hyperscale
DePIN doesn't pose technical challenges — the on-chain part is usually a tiny fraction of the architecture, and the smart contracts platform itself is a sufficient framework.
Token for DePIN rewards
You're better off with discrete tokens for pure-play services rather than muddying up tokenomics that exist to fulfill concrete security goals.
His role vs XRD price
He builds technology and can't solve every problem; whether XRD benefits is outside his domain, though he works hard to be competitive with the market.
Keeping the channel open
Without Radix there'd be no Telegram channel; he keeps it open to share enthusiasm for consensus and answer questions, because Radix people care about this stuff.
El concepto de la semana
The Lottery— A jury you can't bribeSeating and releasing co-hosted validators on running shards is the practical foundation for trickle rotation — the one-seat-at-a-time committee change that disperses corruption while keeping shards live.
hyperscale.rs/kleroterion Jerga, descifrada
Anchor — A known-good checkpoint in a shard's history that recovery can safely rebuild from.
Co-hosted validator — Multiple validator identities running on the same physical machine, which is how vnodes work.
Frontier — The leading edge of a shard's chain that recovery must preserve before discarding.
Dónde aterrizó el trabajo
validator seating and release on running shards
forked shard rebuild from anchors before seating
halt recovery sims on co-hosted layouts
Referencia — mapa de conceptos, hoja de ruta y enlaces▾
El panorama completo
The ClockConsensus-attested time across independent shards.
The CensusThe leaderless beacon of validators, stake and shards.
The OverlapWhy two conflicting blocks can never both commit.
The GeneralsAll-or-nothing cross-shard commits, computed not voted.
The ArchiveEvery published byte is preserved or provably expired.
The LibraryAll state in one merkle tree; a shard is a subtree.
The WillHow in-flight transactions settle when a shard dies.
The LotteryRandom, ever-moving committees; proven cheats are jailed.
The TriageUnder overload, urgent traffic never waits for bulk.
The GovernorValidator entry is re-priced every epoch, like a market.
The Crash LabThe simulator that replays any failure byte-for-byte.
The ProofProving safety with maths, not just tests.
The AsterisksEvery design's trade-offs — including Hyperscale's own.
El camino a mainnet
✓ M1
Adaptive Sharding
~4 mo
Ahora: Milestone 2 · Radix Engine — Week 9 · since August 2026. Desde el día uno: 5,133 commits — un solo desarrollador, totalmente en público.
Enlaces
¿Preguntas? flightofthefox siempre está feliz de conversar en el Telegram de la comunidad.
Escrito por IA a partir de commits públicos, el chat de la comunidad y hyperscale.rs — puede contener errores. · generado 2026-10-05