Previously: Milestone 1 had just kicked off — the 18-month build was officially underway, but the first week was a quiet one with no code landing yet.
The quiet week is over — real code is now landing. flightofthefox scaffolded the beacon — the slow coordination chain that tracks validators and the shard map — along with its sub-consensus machinery, and reshaped the production node around a 'thread-per-shard' model. The foundations of M1 are starting to take visible shape.
Commits / day
peak 70/day · 7/7 days active
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built
The beacon finds its footing
flightofthefox scaffolded the beacon crate — the slow chain that tracks validators and topology — with sub-consensus state machines, randomness reveals, recovery machinery, and stake accounting. This is the Census of the network coming into existence.
→ see “The Census” on hyperscale.rsOne thread per shard
The production node was reworked so each hosted shard runs on its own pinned thread, with its own state, metrics, and event loop. This is the operational skeleton that lets many shards run side by side cleanly.
→ see “The System” on hyperscale.rsCleaner cross-shard paths
flightofthefox tightened the logic for cross-shard transactions: ownership, provisions, and dedup paths are now more reliable. Transactions that touch multiple shards should commit more predictably.
→ see “The Generals” on hyperscale.rsThe bottom line
Standout change
The beacon crate — the slow coordination chain that tracks validators and the shard map — is now scaffolded with its sub-consensus state machines.
What's next
Likely next: wiring the beacon into the production node and expanding the recovery and witness machinery so validators can be safely rotated in and out.
Heard in the chat
The mood: A quiet week in the chat — flightofthefox heads-down on code, no public messages.
This week's concept
The Census— The beacon that tracks validators & topologyThe beacon is the slow chain that tracks validators, stake, and the shard map — the heart of the system's coordination. Scaffolding it this week means the foundations of M1 are now visible in code.
hyperscale.rs/census Jargon, decoded
VRF — A cryptographic lottery ticket — a number anyone can verify was generated fairly, used here to randomly assign validators to jobs.
Epoch — A fixed time window after which the network reshuffles which validators are in charge of which shard.
Quorum certificate — A signed receipt from a majority of validators that a decision has been agreed upon.
Where the work landed
crate scaffolded, sub-consensus state machines added
reworked around a thread-per-shard model
cross-shard provisions and ownership tightened
Reference — concept map, roadmap & links▾
The full picture
The ClockConsistent time across independent shards.
The WillProtects transactions caught in a reshape.
The ProofProving safety with maths, not just tests.
The road to mainnet
Now: Milestone 1 · Adaptive Sharding — Week 4 · ~month 1 of 4 · 24%. Since day one: 2,324 commits — one developer, fully in public.
Links
Questions? flightofthefox is always happy to discuss in the community Telegram.
Written by AI from public commits, the community chat and hyperscale.rs — may contain mistakes. · generated 2026-07-09