Skip to content

v10.0.8

Choose a tag to compare

View all tags
@Jurij89 Jurij89 released this 17 Jul 09:39
v10.0.8
This tag was signed with the committer’s verified signature.
Jurij89
SSH Key Fingerprint: lVBVVXyn/nP0Hc6Zr6wvYaMbezap76qVhFLCNoUG4Qo
Verified
Learn about vigilant mode.
68bf2e7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[10.0.8] - 2026-07-17

Durable-sync materialization hardening for large private Context Graphs. This release makes durable catch-up survive transport drops, responder restarts, and multi-million-quad snapshots without discarding verified work, and fixes the relay and dial paths that stalled fan-out under load. Validated by a 500-Knowledge-Asset private-CG late-join scale test on Gnosis mainnet (5,337,721 unique quads, exact per-graph digest verification). No smart-contract changes — no deployment required (no Solidity source, ABI, or deployment-registry changes since 10.0.7).

Fixed

  • Durable sync survives transport drops without losing verified work (#1775): a requester now retains its verified prefix and accepted-session checkpoints when a stream drops mid-transfer, resuming the same responder row list instead of restarting the snapshot. Responder sessions are persisted with their checkpoints, expired sessions rotate immediately, and store-fallback session expiry slides while a transfer makes progress.
  • Snapshots beyond one million rows no longer fail integrity verification (#1775): the responder clamped any requested cursor to 1,000,000, which silently replayed the row slice at the clamp boundary while the requester kept advancing — producing duplicates and failing manifest verification on any snapshot larger than the cap. Valid non-negative cursors are now accepted in full; exact-graph paging still bounds the response by returning an empty page past the plan.
  • Durable settlement is serialized per graph (#1775): concurrent settlement for the same graph no longer interleaves, and a catch-up round that fails against every peer surfaces the failure instead of reporting a silent no-op success.
  • Catch-up honors its durable time budget (#1775), and durable-only recovery is supported as a safe path.
  • Rootless chain identities reconcile during sync (#1775).
  • Relay fan-out no longer stalls behind stale direct dials (#1775): pooled messages reuse a live relay connection, and the dial path falls back to a live relay after a stale direct dial rather than blocking.

Changed

  • Publisher wallet jobs run concurrently (#1775): each configured wallet owns an independent nonce stream, so a cycle now dispatches one job per wallet in parallel and waits for all to settle. Adding publisher wallets now actually increases throughput. Errors propagate only after every wallet in the cycle settles.
  • Rootless durable batches skip legacy partitioning (#1775).
  • Dashboard SQLite schema 29 → 30 (#1775): sync_checkpoints gains nullable responder_session_id and responder_session_expires_at columns, added idempotently on upgrade. The migration is additive, so rolling back to 10.0.7 is safe — the older schema guard ignores a newer database and leaves the extra columns in place.
  • Release version set: all workspace packages move together to 10.0.8.

Deployment

  • No contract changes in this release. No Solidity source, ABI, or mainnet/testnet deployment-registry files changed since 10.0.7; nodes can upgrade through the normal npm release path.

Full diff: v10.0.7...v10.0.8

Assets 2
Loading