Skip to content

DKG v10.0.14 — Faster, safer publishing and syncing

Latest
Latest

Choose a tag to compare

View all tags
@branarakic branarakic released this 25 Aug 08:10
· 14 commits to main since this release
v10.0.14
780f14a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

DKG v10.0.14 — Faster, safer publishing and syncing

DKG v10.0.14 makes publishing and syncing faster, safer, and more dependable. Nodes can recover interrupted publications using chain evidence instead of retrying blindly, selected public graphs continue syncing across partial progress, and large recovery workloads are divided into bounded batches to keep nodes responsive. Restart recovery and general runtime efficiency are also improved, with no smart-contract deployment required.

npm: @origintrail-official/dkg@10.0.14 — dist-tags latest, mainnet, testnet

Highlights

  • Safer publishing recovery: interrupted transactions are reconciled against chain evidence, preventing speculative retries and duplicate publication.
  • More reliable selected-public syncing: synchronization continues across partial results and temporary provider gaps.
  • Better syncing performance: Verifiable Memory recovery groups assets into bounded, footprint-aware batches.
  • Improved restart behavior: persisted graph subscriptions resume automatically when the daemon starts.
  • More responsive nodes under load: scheduler, storage, networking, query, CLI, and UI improvements reduce unnecessary work and contention.
  • Cleaner memory convergence: finalized Verifiable Memory can safely retire its exact stale Shared Memory copy.

Upgrading from 10.0.13

chain.finalityConfirmations now controls mined-transaction confirmation depth. The default remains 1, prioritizing publishing throughput over an additional reorganization buffer.

Applications that directly construct the publisher from @origintrail-official/dkg-publisher must replace chainRecoveryResolver with the new chainProofResolver contract. Regular node operators are unaffected.

After upgrading, operators should inspect previously failed publisher jobs with:

dkg publisher jobs --status failed

Legacy held jobs should be cleared individually only after their chain state has been verified.

The dashboard database upgrades automatically from schema 32 to 33. Graph data is retained.

Validation

Distributed release validation published and synchronized all 500 Shared Memory assets and 497 Verifiable Memory assets. Both remote nodes received every published asset with zero missing or mismatched pairs. Three unpublished VM cases were accepted under a documented release waiver; this is not presented as a strict 500/500 VM result.

Selected graph convergence in this release applies to publicly readable Context Graphs. Existing private encrypted live-sharing behavior is unchanged.

No smart-contract, ABI, or network deployment changes are required.

Full changelog: v10.0.13...v10.0.14

Assets 2
Loading