Releases: OriginTrail/dkg.js
dkg.js 8.0.7 Release
Description
We’re thrilled to announce the release of dkg.js 8.0.7 with support for paranets on OriginTrail Decentralized Knowledge Graph with many new exciting features.
You can now use paranets with your AI agents, control which Knowledge Assets get published on your paranet, incentivize knowledge mining with multiple tokens, and much more!
🚀 Key updates
- Knowledge Curation - using the new data staging feature, Knowledge Curators can control which Knowledge Assets get included in a paranet.
- Knowledge Miners stage their knowledge assets to the paranet for review before they are included.
- Curators (assigned by the Paranet operator) review and accept or decline knowledge submissions, based on their custom logic (e.g. Proofs of Knowledge)
- Incentive Pools - Deploy incentive pools with any ERC20 or native token to incentivise knowledge miners.
- Multiple Incentive Pool support - Deploy multiple incentive pools with different incentive tokens for more flexible incentives.
More info: docs.origintrail.io
Join the discussion in Discord
dkg.js 8.0.6 Release
The 8.0.6 release brings dependency update of assertion tools.
dkg.js 6.5.3 Release
Description
The 6.5.3 release of dkg.js brings multiple important enhancements to ensure better experience for developers.
🚀 Features
- Improved return objects for all operations
- Statuses of all operations performed on DKG Nodes
- Transaction receipts for all transactions
- Optional await for transactions finalization on Neuroweb
#TraceOn
dkg.js 6.5.2 Release
Description
The 6.5.2 release of dkg.js brings multiple important enhancements and fixes to ensure better experience for developers.
🚀 Features
- Optional force replacement of pending transactions with gas price detection and incrementation
- Optional transaction simulations with "eth_call" in order to catch proper EVM error messages
- Optional gas limit multiplier
- Optimized event logs parsing
🐛Bug fixes
- Fixed allowance handling logic
- Fixed returned object for setAllowance function
- Fixed GET protocol for non-private KAs
- Fixed contract addresses fetching without proper blockchain metadata initialization
#TraceOn
dkg.js 6.5.0 Release
We're thrilled to announce the release of dkg.js v6.5.0, with full support for DKG on the BASE blockchain! 🌐 This update means your dkg.js client can seamlessly interact with DKG on BASE, unlocking new realms of possibility and innovation. Dive in and harness the power of this DKG on BASE today!
🚀 Features
BASE integration #139
#TraceOn
dkg.js 6.4.0 Release
Description
- The dkg.js 6.4.0 release is introducing Paranets - on-chain autonomous AI systems for collective building of knowledge graphs with knowledge mining incentives! Features in this release allows developers to create, manage, and utilize Paranets effectively. How to interact with Paranets using dkg.js read here.
🚀 Features
- Create Paranet
- Deploy NEURO Incentives contract
- Create Paranet AI Service and add to a Paranet
- Check and claim rewards for knowledge miners, operators and voters
- Query a specific Paranet
- Federated SPARQL Queries
#TraceON
dkg.js 6.3.0 Release
Description
- The 6.3.0 release brings enhancements that support the staking release on NeuroWeb for DKG.
🚀 Features
- Scoring function ID constants update: Scoring function ID updated to correspond to new scoring functions used on NeuroWeb with value 2 (#136).
#TraceON
dkg.js 6.2.1 Release
Description
With the 6.2.1 release, the dkg.js client gives more power to users by enriching the array of choices for retrieving bid suggestions.
🌟Improvements
- Bid Suggestion Flexibility: Added a new parameter to the getBidSuggestion, allowing users to specify a preference for low, medium, high, or getting all three bid suggestions (#135).
#TraceON
dkg.js 6.2.0 Release
Accompanying release to DKG V6.2.0 with Delegated staking release
dkg.js 6.1.2 Release
Description
In dkg.js 6.1.2 we have included an improvement where we changed the order of operations in knowledge asset creation. Client will now first send a replication request to the network, and only if that is successful, it will proceed and send request to connected node store it also in his triple store.
Improvement
- First send replication to the network, after that request for storing on local node (#127)
#TraceOn