Releases: OriginTrail/ot-node
OriginTrail Release v4.1.15
OriginTrail Release v4.1.14
Changes
This release enables the optimization introduced in the previous release to greatly improve the possible message throughput during replication, reducing the number of failed replications and enabling more nodes to apply for an offer.
OriginTrail Release v4.1.13
OriginTrail Release v4.1.12
OriginTrail Release v4.1.11
v4.1.10
This release fixes an issue where an older node would generate a new network identity every time it is started. It also fixes a 🐛 where network communication can get mixed up between different networks
🐛 Bug Fixes
OriginTrail Release v4.1.9
🐛 Bug Fixes
- Bugfix for payout command (#1327)
OriginTrail Release v4.1.8
🚀 Features
- Implement trail reach parameter with extended and narrow option (#1312)
- Added script for backup and upload data to AWS S3 instance (#1304)
- Enabled OT-JSON version 1.2 (#1313)
🐛 Bug Fixes
- Better handling of GS1-EPCIS or WOT export after OT-JSON import (#1309)
- Added a 30 minute period to existing payOut commands (#1305)
🧰 Maintenance
OriginTrail Release v4.1.7
Changes
This release patches an important issue we've observed with the dataset processing functionalities and message routing protocol, covering potential cases when data integrity values could be miscalculated. Also, this release introduces support for new OT-JSON version 1.2 for importing, exporting, and replicating datasets on the nodes, which will ensure better and more consistent sorting approach and reliable results when verifying the data integrity. This release patches issue with delayed offers by preserving database records for delayed offers.
🧰 Maintenance
Added support for OT-Json version 1.2 (#1301)
🐛 Bug Fixes
Preserve handler_id for a delayed offer (#1295)
Sort routing messages in data integrity validation process (#1291)
OriginTrail Release v4.1.6
Hotfix
This release applies a patch in the dataset processing functionalities, covering potential cases when data integrity values could be miscalculated.