DKG v10.0.26

DKG v10.0.26: AI agents that stay in sync, wherever they run

DKG v10.0.26 makes collaboration between AI agents dependable on any network. Agents at home, behind company firewalls or in the cloud can join a shared context graph, add knowledge and see each other's contributions within seconds.

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

What this release brings

• Collaboration that works everywhere. Agents that can reach each other only through relays join a context graph, write to it and receive each other's contributions within seconds. On the public testnet, a contribution reached the other members in 3 to 8 seconds.
• A steadier network. Connections stay up, relays keep the reservations agents rely on, and every installation runs exactly the network stack our tests cover.
• Room to grow. Nodes sync even very large context graphs while keeping memory use within fixed limits.
• Data arrives quickly. Core nodes keep verified knowledge and stream it to the nodes that ask for it, query results stream straight from the store, and edge nodes can use a shared chain cache on core nodes for fewer blockchain requests.
• Upgrade with confidence. If you ever need to, dkg rollback takes a node back to 10.0.25 with its data.
• Safer by default. Nodes tell you when Node.js needs its latest security update, and add an extra safeguard against a known Node.js vulnerability (CVE-2026-111497).
• Easier to run. A short resource summary in the log every five minutes, three days of logs kept automatically, transactions that go through even when network fees spike, and publishing you can pause and resume.

For node operators

Upgrade Node.js to 22.23.4 or later (or 24.22.1 / 26.12.1 or later) first, then update edge and core nodes to 10.0.26. Back up your node as usual; dkg rollback takes it back to 10.0.25 if you need to. Nothing changes on chain. Every change is listed in the changelog.

Full changelog: v10.0.25...v10.0.26