10.0.22

Patch after 10.0.21. Already on testnet-canary: the fixes merged after the 10.0.21 cut. Request admission at start-up: background authority reads admitted within their deadline (#3038), one shared chain adapter initialization (#3043), state kept on an unanswered authority read (#3042), and local-chain request budgets for devnet and the live-daemon tests (#3040, #3032). Carried over from 10.0.21: the known issues of its release notes, its open bugs, and the September sweep PRs that merge cleanly or need only a small rebase. No contract, wire-format or default changes; anything operator-visible gets an Upgrading row. #3038 and #3043 change how every chain request is admitted, so the candidate gets a testnet soak before promotion.

Navigation Menu

10.0.22

fix(chain): admit background authority reads within their deadline

fix(chain): share one adapter initialization between concurrent callers

fix(agent): keep gossip and catalog state on an unanswered authority read

RFC-64 author-head replay loop saturates an author (≈14k replays/10 min) and starves joins and SWM sync

Peers that connect while both are starting never see each other's sync support

A member added to a private Context Graph only by wallet address does not receive its shared memory until it joins

A restarted member Edge does not reconnect to its private graph's curator Edge

VM refresh after KA updates: durability, batching and bounds follow-ups

Chain-promote sweep starves live finalizations on graphs that keep deferring

Ontology serving gate opens while unclassified legacy bindings remain in ontology

RFC-64 status reports complete when a retained replay promise has the same row count as the applied head

A 3 s identity probe timeout locks a slow peer out of admission for minutes

A dial by peer id with a caller signal has no deadline and can stall a graph's VM reconcile

Investigate recurring main-thread pauses across mainnet cores, including 10.0.19

bug: 10.0.21 devnet member SWM share fails on unavailable graph authority

Issues