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.

v2.1.5-rc.1

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

v2.1.4

This release brings several improvements, optimizations, and new features that enhance the functionality and robustness of the Thor platform. With a focus on expanding smart contract testing capabilities, improving debugging, and providing more flexible node operations, this update makes Thor even more efficient for developers and node operators.

What's Changed:

• Mempool Optimization: Introduced a new CLI option --limit-per-account to control the number of transactions per account in the mempool, enhancing transaction flow management. (#815)
• Dynamic Log Verbosity: Node operators can now adjust log verbosity in real-time without needing to restart the node, providing greater flexibility in debugging and monitoring. The --enable-admin enables log verbosity adjustment server. (#799)
• Allowed Tracers Flag: Added a new --api-allowed-tracers flag, giving operators control over which tracers are allowed, improving security and resource management. (#823)
• Justified Revision: Added support for justified revision in the API server, enhancing the accuracy of block validation processes. (#802)
• Code Linting: Added revive linter for improved code quality checks, ensuring consistent coding standards. (#838)
• Mempool Pending Cost Tracking: Implemented tracking of pending transaction costs per payer, providing better visibility into transaction acceptance into the mempool. (#845)

Contributors

@libotony
@otherview
@darrenvechain
@paologalligit
@MakisChristou

New Contributors:

@nwbrettski made their first contribution in this release (#819).

Full Changelog: v2.1.3...v2.1.4

v2.1.4-rc.3

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

v2.1.4-rc.2

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

v2.1.4-rc.1

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

v2.1.3

This release focuses on enhancing functionality, boosting reliability, and optimizing key features, contributing to the superior overall performance of the software. Among the updates, two enhancements stand out:

• Revision Next for Call/Estimate Endpoints: We've added revision next, which adjusts the execution context to the upcoming block (both block number and timestamp). This feature is recommended for all clients to significantly enhance user experience by ensuring more precise and timely data handling.

• Max Log Entries Allowed Feature: To improve server stability, we have implemented the max-log-entries-allowed feature in the logs endpoint. A new flag, --api-logs-limit (default set to 1000), allows node operators to control the volume of log entries, helping maintain optimal system performance.

What's Changed

• Upgraded go-sqlite version to latest.
• Upgraded golang to version v1.22.
• Enabled injection of the master key via standard input.
• Transitioned to a more robust logging system using slog.
• Added flag --json-logs to enable output logs in JSON.
• Enhanced metrics for websockets and node stats.
• Various enhancement test coverage improvement.

Contributors

• @libotony
• @otherview
• @darrenvechain
• @paologalligit
• @MakisChristou

Full Changelog: v2.1.2...v2.1.3

v2.1.3-rc.2

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