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% 지난주 대비
줄 변경
일별 커밋
최고 16/일 · 7일 중 2일 활동
모멘텀
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.
→ hyperscale.rs에서 “The Clock” 보기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.
→ hyperscale.rs에서 “The Overlap” 보기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.
→ hyperscale.rs에서 “The Crash Lab” 보기핵심 정리
가장 돋보인 변화
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.
다음 계획
Likely next: finishing the fetch-grace and sync floors around adopted certificates, plus more simulator coverage for the fork scenarios.
채팅방에서 들려온 이야기
분위기: 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, 커뮤니티 텔레그램에서
이번 주의 개념
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 용어 풀이
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.
작업이 닿은 곳
certificate acceptance rules reworked
high-QC gate and restart floors
fast sims guarding split and sync rules
참고 — 개념 지도, 로드맵 & 링크▾
전체 그림
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.
네 가지 부분
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
막대는 이번 주 변경된 코드 줄의 비율입니다. 공통 기반 작업은 Foundations & reliability로 집계됩니다. 첫날부터 지금까지: 6,138 커밋 — 개발자 한 명, 전 과정 공개.
링크
궁금한 점이 있나요? flightofthefox는 언제든 커뮤니티 텔레그램에서 대화를 환영합니다.
공개 커밋, 커뮤니티 채팅, hyperscale.rs를 바탕으로 AI가 작성 — 오류가 있을 수 있습니다. · 생성 2026-11-16