v2.2.1

⚠️ If upgrading from version before 2.2.0 a full resync is required ⚠️ 

Please refer to the Migration Guide if required.

---

What's Changed

• Fixed a bug in the events range finder

Contributors

• @darrenvechain
• @otherview

Full Changelog: v2.2.0...v2.2.1

v2.2.1-rc.2

What's Changed

• Update from go-eth upstream by @otherview in #971

Full Changelog: v2.2.1-rc.1...v2.2.1-rc.2

v2.2.1-rc.1

What's Changed

• fix: using from instead of to by @darrenvechain in #968

Full Changelog: v2.2.0...v2.2.1-rc.1

v2.2.0

⚠️ There is a known issue with the event request range when using a particular time - Fixed in v2.2.1 ⚠️ 

⚠️ This Version Requires a Full Resync ⚠️ 

Please refer to the Migration Guide if required.

---

What's Changed

• Major refactor to the main DB, significantly improving storage space and sync performance
• Minor storage improvement to the LogsDB, trimming leading zeros in all topic values
• Optionally return transaction and log indexes in /logs endpoints responses
• Various improvements to the metrics, subscriptions and txpool packages

Contributors

• @libotony
• @otherview
• @darrenvechain
• @freemanzMrojo
• @paologalligit
• @MakisChristou
• @qianbin
• @YeahNotSewerSide
• @jsvisa

New Contributors

@vanja-vechain made their first contribution in #955

Full Changelog: v2.1.6...v2.2.0

v2.2.0-rc.3

Superseded by v2.2.0

v2.2.0-rc.2

Superseded by v2.2.0-rc.3

v2.2.0-rc.1

Superseded by v2.2.0-rc.2

v2.1.6

Thor v2.1.6 Release Notes

This release focuses on improvements, documentation updates, and monitoring enhancements for developers and node operators, ensuring a more streamlined and transparent experience.

What's Changed

• Update DockerHub Description on Release: Improved DockerHub release descriptions for better clarity and usability. #921 by @darrenvechain
• Extract CacheStats for Monitoring: Added cachestats to record cache performance metrics, enabling better observability of caching behavior. #924 by @libotony
• API Documentation Updates: Enhanced and updated the API documentation for improved developer guidance. #925 by @darrenvechain

---

Contributors

• @darrenvechain
• @libotony

Full Changelog: v2.1.5...v2.1.6

v2.1.5

This release introduces Thor v2.1.5, featuring significant enhancements, new tools, and performance optimizations for developers and node operators. With the debut of thorclient, a Go-based client for interacting with the VeChainThor blockchain, as well as improvements to subscription performance, debugging tools, and API configurations, this update empowers a smoother and more efficient development experience.

What's Changed:

• Thor Client Released: Introduced thorclient, a Go client library enabling developers to interact with VeChainThor accounts, transactions, blocks, events, and other blockchain features via HTTP and WebSocket connections. (#818, #908)
• Subscription Endpoint Caching: Added a simple cache to the beat, beat2, and block subscription endpoints, enhancing CPU performance during high on-chain traffic and heavy subscription loads. (#866)
• Deprecated Endpoints Disabled by Default: Deprecated endpoints are now disabled by default, improving security and resource allocation. Use the --api-enable-deprecated flag to re-enable these endpoints if necessary. Deprecated endpoints include POST /accounts, POST /accounts/{address} and WebSocket /subscriptions/beat (#897)
• Raw Query Support for Blocks Endpoint: Added support for the raw query parameter in the /blocks endpoint, returning RLP-encoded block headers for block signature verification. (#899)
• Node Health Endpoint: Introduced a node health API endpoint, enabling quick evaluation of node health through metrics such as blockchain progress and peer connectivity. (#836)

Contributors

@libotony
@otherview
@darrenvechain
@paologalligit
@MakisChristou
@YeahNotSewerSide
@jsvisa

New Contributors

• @YeahNotSewerSide made their first contribution in #899
• @jsvisa made their first contribution in #905
• @freemanzMrojo made their first contribution in #915

Full Changelog: v2.1.4...v2.1.5

v2.1.5-rc.2

This is a release candidate, please refer to v2.1.5 release notes.