Releases: OriginTrail/ot-node
OriginTrail Release v4.1.5
Changes
🚀 Features
Expanded get dataset info API and moved method to info controller (#1280)
🧰 Maintenance
Prepared Holding contract to reduce the gas cost for offers (#1281)
Prepared Profile contract to increase minimal stake (#1277)
🐛 Bug Fixes
Fixed OT-JSON v1.1 export signature sort issue (#1286)
OriginTrail Release v4.1.4
Hotfix
This release patches an important issue we've observed with the sorting of the new OT-JSON 1.1 version when exporting a dataset, enabling more reliable results when verifying the dataset signature.
OriginTrail Release v4.1.3
Changes
- Updated node info route, now it's sending graph cardinality info (#1270)
🚀 Features
- Added update price factor script (#1267)
- Generate unique graph database password as default (#1266)
- Enable OT-JSON Version 1.1 (#1265)
🐛 Bug Fixes
- Resolved unhandled exception: Timed out waiting for response (#1269)
OriginTrail Release v4.1.2
OriginTrail Release v4.1.1
OriginTrail Release v4.1.0
OriginTrail Release v4.0.10
Breaking Change
We’ve removed the support for reading the node_wallet and node_private key from the environment configurations. Your node_wallet and node_private_key MUST be stored in your JSON configuration file.
If not provided, your node will show an error message stating “Please provide a valid wallet!”. In this case, add the node_wallet and node_private_key to your JSON configuration file (usually named .origintrail_noderc) and restart your node.
This release also improves the performance of the export process and enables OriginTrail Network Explorer to display results faster.
🚀 Features
- Add combined read & export API route (#1211)
- Refactor export route to be non blocking api call (#1207)
- Add bash script for restoring node from backup (#1209)
🐛 Bug Fixes
- Cleaning challenges from database when offer is no longer active (#1201)
🧰 Maintenance
OriginTrail Release v4.0.8
Changes
This release brings a substantial improvement to how messages are routed through the peer-to-peer network, which aims to drastically increase the possibility of two nodes to communicate directly.
We expect this to increase the challenge success rate on the network and reduce the number of litigations that are initiated due to network communication limitations.
🚀 Features
- Improved the Kademlia direct message routing (#1193)