V8.2.5 Mainnet Node Release

This Mainnet release brings improvements to the publish process, enhanced logging for easier debugging, and a cache cleanup fix that ensures assets are finalized correctly once the required number of approvals has been reached.

🌟 Improvements

  •  Improved publish flow now completes as soon as the minimum acknowledgements are reached and skips redundant processing once minAcksReached is set, only failing when all contacted nodes respond unsuccessfully
  •  Cache handling logs are more descriptive and downgraded to warnings for cache-miss scenarios, reducing noise while still emitting important state changes
  •  Blazegraph write failures now log HTTP status codes along with response and query snippets to aid debugging
  •  Memory cache cleaner now runs every 1 hour, while disk cache cleaner continues to run every 24 hours
  •  Publish replication now enforces the on-chain minimumRequiredSignatures: client requests are clamped so they can’t set a replication count below the contract’s minimum (higher values still allowed).

🐛 Bug Fixes
  •  Fixed asset finalization to ensure all nodes correctly finalize assets once the required number of approvals has been reached

DKG Core Node runners, make sure to update your nodes!
Trace On!

The V8.2.4 Testnet node release includes a cache cleanup fix that enables all nodes to finalize assets once the required number of approvals has been reached.

🐛 Bug fix

• Fix asset finalization once the required number of approvals has been reached.
• The memory cache cleaner now runs every 1h, disk cache cleaner runs every 24h as before

DKG Core Node runners, make sure to update your nodes!
Trace On!

The V8.2.3 Testnet node release improves the publish process and adds additional logs for easier debugging.

🌟 Improvements

• Improved publish flow now completes as soon as the minimum acknowledgements are reached and skips redundant processing once minAcksReached is set, only failing when all contacted nodes have responded unsuccessfully
• Cache handling logs are more descriptive and downgraded to warnings for cache-miss scenarios to avoid noisy errors while still emitting state changes
• Blazegraph write failures now log HTTP status plus response/query snippets to aid debugging

DKG Core Node runners, make sure to update your nodes!
Trace On!

The V8.2.2 Testnet node release brings a bug fix for metadata retrieval in GET operations.

🐛 Bug fix

• Fixed incorrect parameter passing in the GET command metadata retrieval

DKG Core Node runners, make sure to update your nodes!
Trace On!

The V8.2.2 node release brings a bug fix for metadata retrieval in GET operations.

🐛 Bug fix

• Fixed incorrect parameter passing in the GET command metadata retrieval

DKG Core Node runners, make sure to update your nodes!
Trace On!

The V8.2.1 release introduces improvements to the auto-updater module and prepares us for the upcoming Github repository rename - the former ot-node repo will be renamed to dkg-engine for better clarity.

✅ If your auto-updater is enabled:

No action is required — your node will automatically update to v8.2.1. Please verify that your node has successfully updated to version 8.2.1 to ensure continued operation after the repository rename.

⚙️ If your auto-updater is disabled:

Make sure to manually update your node within the next 24 hours. This update is required before the GitHub repository name changes to ensure your node continues receiving future updates.

🧩 If you do not update to 8.2.1 before the rename

You'll need to manually update your auto-updater configuration:

1. Enter your node directory: cd ot-node/current/
2. Update the auto-updater repository URL by executing: sed -i 's|OriginTrail/ot-node|OriginTrail/dkg-engine|g' src/modules/auto-updater/implementation/ot-auto-updater.js
3. Verify the changes by checking lines 10 and 11 in src/modules/auto-updater/implementation/ot-auto-updater.js They should look as follows:

const REPOSITORY_URL = 'https://github.com/OriginTrail/dkg-engine';
const ARCHIVE_REPOSITORY_URL = 'github.com/OriginTrail/dkg-engine/archive/';

Trace On!

The V8.2.1 release introduces improvements to the auto-updater module and prepares us for the upcoming Github repository rename - the former ot-node repo will be renamed to dkg-engine for better clarity.

✅ If your auto-updater is enabled:

No action is required — your node will automatically update to v8.2.1. Please verify that your node has successfully updated to version 8.2.1 to ensure continued operation after the repository rename.

⚙️ If your auto-updater is disabled:

Make sure to manually update your node within the next 24 hours. This update is required before the GitHub repository name changes to ensure your node continues receiving future updates.

🧩 If you do not update to 8.2.1 before the rename

You'll need to manually update your auto-updater configuration:

1. Enter your node directory: cd ot-node/current/
2. Update the auto-updater repository URL by executing: sed -i 's|OriginTrail/ot-node|OriginTrail/dkg-engine|g' src/modules/auto-updater/implementation/ot-auto-updater.js
3. Verify the changes by checking lines 10 and 11 in src/modules/auto-updater/implementation/ot-auto-updater.js They should look as follows:

const REPOSITORY_URL = 'https://github.com/OriginTrail/dkg-engine';
const ARCHIVE_REPOSITORY_URL = 'github.com/OriginTrail/dkg-engine/archive/';

Trace On!

The V8.2.0 Mainnet node release brings improvements to node performance

🌟 Improvements

• Remove Blazgraph restarts
• Reduced load and improved query performance of operational DB
• Improved triples insertion

DKG Core Node runners, make sure to update your nodes!
Trace On!

The V8.1.1-rc.12 Testnet node release brings improvements to node sync and expands on KA metadata functionalities

🌟 Improvements

• Enabling fetching full metadat when KA is requested
• Disabling restarting Balzegraph when status can't be fetch
• Decreasing number of nodes pulled per batch in batch get

DKG Core Node runners, make sure to update your nodes!
Trace On!

The V8.1.1-rc.11 Testnet node release brings further improvements to node health

🌟 Improvements

• Improved triple store interaction with batch insert

• Improved operationalDB usage by reducing nthe umber of writes and updates to reduce load on the DB

DKG Core Node runners, make sure to update your nodes!
Trace On!