Skip to content

Releases: vechain/thor

v2.4.2

13 Feb 11:18
eebc301

Choose a tag to compare

Important

Optional but highly recommended upgrade.
v2.4.2 is a hardening release. No protocol fork is activated, and operators can upgrade in-place.

What's Changed

New Contributors

Full Changelog: v2.4.1...v2.4.2

v2.4.2-rc.1

12 Feb 11:04
eebc301

Choose a tag to compare

v2.4.2-rc.1 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v2.4.1...v2.4.2-rc.1

v2.4.1

22 Jan 10:50
932ec4c

Choose a tag to compare

Important

Optional but recommended upgrade.
v2.4.1 is a stability & hardening release. No protocol fork is activated, and operators can upgrade in-place.

Optional event/transfer logs performance improvement:
This release introduces an optional flag to create additional indexes for faster log queries: --logdb-additional-indexes.
After this flag is enabled, a migration will be performed. On a fully synced mainnet node, the process may take tens of minutes, depending on the hardware specifications, during which the API server will be temporarily unavailable.

VeChainThor v2.4.1

What's Changed

v2.4.1 focuses on correctness, safety, and operational robustness following the Hayabusa transition, with targeted improvements across arithmetic safety, txpool behavior, Solo/test stability, and developer/operator ergonomics.

Security & Correctness Hardening

  • Added additional underflow/overflow protections across critical calculations, including stricter uint64/int conversions and use of safe arithmetic helpers.
  • Fixed a panic condition that could cause the node to exit unexpectedly under specific runtime conditions.
  • Corrected a big integer comparison bug in Solo mode that could lead to incorrect block validation.
  • Fixed a resource leak by ensuring HTTP response bodies are always closed after use.

Performance, Txpool & Consensus Robustness

  • Refactored and cleaned up the packer loop to improve block packing efficiency and long-term maintainability.
  • Improved transaction ordering with non-local tx priority handling in the txpool.
  • Fixed a priority price calculation bug that could affect transaction fee estimation.
  • Improved finality handling in await-until-steady for more robust consensus waiting.
  • Enhanced on-demand Solo mode to prevent block production with past timestamps.

APIs & Developer Tooling

  • Added a raw storage retrieval API for direct access to blockchain state.
  • Added build version information to API responses for easier debugging and version tracking.
  • Thorclient improvements.

Observability & Operator Experience

  • Enhanced logging infrastructure with configurable log levels and improved error reporting.
  • Slow query logging is disabled by default to avoid unnecessary production overhead.
  • Extended the --network flag to support both short and long forms (main/test and mainnet/testnet).
  • Added optional additional log indexes for improved log query performance via --logdb-additional-indexes.

CI, Build & Test Reliability

  • Increased and consolidated test coverage, including richer staker validation and permutation testing.
  • Added and updated Go 1.25 support in build and test configurations.
  • Updated Docker base images and Solidity Docker image used for contract compilation.

Contributors

Huge thanks to everyone who brought Hayabusa to life:


Full Changelog:
v2.4.0...v2.4.1

v2.4.1-rc.2

16 Jan 13:52
932ec4c

Choose a tag to compare

v2.4.1-rc.2 Pre-release
Pre-release

Superseded by v2.4.1

v2.4.1-rc.1

14 Jan 14:22
fe74490

Choose a tag to compare

v2.4.1-rc.1 Pre-release
Pre-release

Superseded by v2.4.1-rc.2

v2.4.0

28 Oct 14:19
95d8cff

Choose a tag to compare

Important

Mandatory upgrade.
This release activates a hardfork. All node operators must upgrade to v2.4.0 before the following block heights:

Hayabusa Hardfork

Testnet Hardfork: Block 23,221,800 ~ Tue, 4 Nov 2025 11:39:30 UTC
Mainnet Hardfork: Block 23,414,400 ~ Tue, 02 Dec 2025 11:27:00 UTC

What’s Changed

Hayabusa marks the beginning of VeChain’s Delegated Proof of Stake (DPoS) era expanding participation, aligning incentives, and setting the stage for scalable community governance.

Named after the pioneering Japanese spacecraft, Hayabusa symbolizes precision, endurance, and innovation reflecting VeChain’s leap toward broader decentralization and network sustainability.

What's Changed

  • Delegated Proof of Stake (DPoS) (VIP-253) transforms the consensus model, allowing VET holders to stake or delegate and directly participate in network security.
  • Dynamic VTHO Tokenomics (VIP-254) replaces static VTHO generation with staking-based block rewards that adapt to network activity and staked supply.
  • Validator Lifecycle Overhaul staking, delegating, renewal, exit, and withdrawal are all managed via the new Staker contract.
  • Stake-Weighted Finality blocks finalize based on validator weight, improving resilience and cryptoeconomic security.
  • Performance & Stability significant optimization to gas usage, storage writes, and housekeeping efficiency.
  • Developer Readiness improved error context, new admin APIs, enhanced Solo/Testnet tooling, and complete Devnet mirror.
  • VTHO Issuance will stop at the above mentioned block heights and will reactivate as block rewards after the successful transition from PoA to DPoS.

Audit Reports

Contributors

Huge thanks to everyone who brought Hayabusa to life:

Special shout-out to the engineering, QA, and research teams for the months of design, iteration, and validation behind Hayabusa - a massive step forward for VeChain’s evolution.

Full Changelog:
v2.3.2...v2.4.0

v2.4.0-rc.2

27 Oct 12:04
95d8cff

Choose a tag to compare

v2.4.0-rc.2 Pre-release
Pre-release

Superseded by v2.4.0

v2.4.0-rc.1

21 Oct 12:19
08ff70d

Choose a tag to compare

v2.4.0-rc.1 Pre-release
Pre-release

Superseded by v2.4.0-rc.2

Full Changelog:
v2.3.2...v2.4.0-rc.1

v2.3.2

29 Sep 12:13
0e840c3

Choose a tag to compare

What's Changed

  • Improved Sync Times

    • Improve node sync times by increasing the buffer size and processing the RLP in parallel. This will drastically decrease the sync time during the initial sync.
  • Improve block propose flow

    • Enhanced the packer flow to determine the optimal timing for scheduling the block proposal, even in cases where the parent block propagation is delayed due to various factors.
  • Logs Events Bug Fix

    • Fix a bug where the logs event endpoint was returning an empty array when options are defined.
  • Minor Improvements and Technical Debt:

    • Add metrics to the disco package.
    • Add bandwidth metrics.
    • Update Swagger UI version.
    • Update README.md.
    • Linter updates.
    • Verify clock offset.

Contributors

Huge thanks to our contributors for this release:


Full Changelog: v2.3.1...v2.3.2

v2.3.2-rc.1

23 Sep 13:26
c090c1a

Choose a tag to compare

v2.3.2-rc.1 Pre-release
Pre-release

Superseded by v2.3.2