VeChain has rolled out Thor v2.4.3 on mainnet, introducing a technical upgrade centered on security hardening, network reliability, and transaction handling.
We just upgraded mainnet – VeChain Thor v2.4.3 is now live!
Our latest update is a security hardening patch that tightens 3 core areas: network robustness, transaction accounting, and API safeguards.
What shipped (and what it means):
Transaction accounting: Pending… pic.twitter.com/gT3Y7fRUw3
— VeChain (@vechainofficial) March 31, 2026
The update is not a headline-grabbing feature release, but it is the kind of maintenance work that matters for any blockchain trying to remain usable and dependable at the infrastructure level. According to VeChain, the patch tightens three core areas: network robustness, transaction accounting, and API safeguards.
Among the more practical changes is an improvement to pending transaction accounting, which should help the network track in-flight transactions more accurately. In real terms, that could reduce issues such as failed, delayed, or stuck transactions — a small but meaningful improvement for both end users and applications operating on the chain.
The release also introduces a maximum gas cap per transaction, a safeguard designed to prevent any single transaction from consuming an outsized share of network resources. While that may sound technical, the goal is straightforward: improve predictability and reduce the risk of resource-heavy activity affecting broader network performance.
For developers, one of the more relevant additions is support for the MCOPY opcode in the runtime. This instruction improves how smart contracts handle memory copying operations, which can translate into more efficient contract execution and potentially lower computational costs for certain applications. That is the kind of backend optimization that does not attract much attention publicly, but can matter over time for developer experience and contract efficiency.
VeChain also removed legacy bootnodes, which are used by nodes when first connecting to the network. Stripping out outdated connection points should help nodes discover peers more quickly and improve overall connection reliability across the network.
At the infrastructure level, the node software’s Go runtime has also been upgraded to v1.26.1, bringing general performance and security improvements from the underlying development stack.
Taken together, Thor v2.4.3 is best understood as a stability and resilience upgrade rather than a strategic product expansion.
That may sound less exciting than a major roadmap announcement, but these types of releases are often more important in practice. For blockchain networks, reliability is not built through one large launch — it is built through repeated upgrades that reduce friction, tighten security, and improve how the system behaves under real usage.
With Thor v2.4.3 now live, VeChain is signaling that it is still focused on that quieter, but essential, part of infrastructure development.
