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.
+2.1k β722
-88% vs last wk
lines changed
Commits / day
peak 16/day Β· 2/7 days active
Momentum
Lines changed / week
last 8 weeks
What flightofthefox built
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.
β see βThe Clockβ on hyperscale.rsA 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.
β see βThe Overlapβ on hyperscale.rsRehearsing 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.
β see βThe Crash Labβ on hyperscale.rsThe bottom line
Standout change
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.
What's next
Likely next: finishing the fetch-grace and sync floors around adopted certificates, plus more simulator coverage for the fork scenarios.
Heard in the chat
The mood: 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, in the community Telegram
This week's concept
The Clockβ A clock made of votesThe 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 Jargon, decoded
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.
Where the work landed
certificate acceptance rules reworked
high-QC gate and restart floors
fast sims guarding split and sync rules
Reference β concept map, roadmap & linksβΎ
The full picture
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.
The four parts
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
Bars show this week's share of lines changed. Shared groundwork counts as Foundations & reliability. Since day one: 6,138 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-11-16