VeChain Interstellar Hardfork Targets September 16, but One EIP Is Still Unclear

VeChainThor’s Interstellar hardfork is expected to activate at block 25,902,540, projected for September 16, 2026, at about 11:15 UTC. The block height is the trigger; the date and time are estimates that can move as the chain’s block production speeds up or slows down.

For ordinary VET and VTHO holders, VeChain says there is no token migration, asset swap or address change. The deadline belongs mainly to validators, public-node operators, exchanges, custodians and application teams—and those technical users have one documentation discrepancy to resolve before treating the upgrade list as final.

What is VeChain’s Interstellar upgrade?

Interstellar is a consensus-breaking upgrade to VeChainThor’s Ethereum Virtual Machine. Its governing document, VeChain Improvement Proposal 255, is designed to move the chain from Ethereum’s Shanghai-era execution features toward changes introduced across the Cancun, Prague and Osaka releases.

That does not turn VeChainThor into Ethereum. VeChain keeps its multi-clause transactions, fee delegation, dual-token VET/VTHO design and its own block-ID format. Ethereum transaction equivalence is explicitly outside VIP-255 and has been deferred to a later proposal.

The upgrade’s practical goal is narrower: reduce friction for modern Solidity and Vyper tooling and provide cryptographic functions that applications increasingly expect. The proposal includes transient storage through TLOAD and TSTORE, the MCOPY memory-copy instruction, updated SELFDESTRUCT behavior, and native operations for the BLS12-381 and secp256r1 curves.

Those curves support use cases such as signature aggregation, zero-knowledge systems and passkey-style authentication. They are not a post-quantum signature migration; readers following that separate issue can see our report on Ethereum’s 2029 post-quantum deadline.

The activation time is an estimate, not an appointment

VeChain’s official account announced block 25,902,540 with an estimated arrival on September 16 at 11:15:10 UTC. That is 7:15 a.m. Eastern Time and 4:15 a.m. Pacific Time, using current U.S. daylight-saving offsets.

A hardfork cannot safely depend on every computer sharing an identical clock. It activates when the canonical chain reaches the configured block. The wall-clock estimate will drift if recent block intervals do. Exchanges and infrastructure providers can therefore pause deposits and withdrawals before the projected time and restore them only after they consider the upgraded network stable.

Trading a token on a centralized exchange is separate from depositing or withdrawing it on the underlying chain. A venue may keep VET trading open while its VeChainThor wallet is temporarily unavailable. Users planning an on-chain transfer should check their venue’s own status page close to the fork instead of relying on a calendar reminder alone.

VeChain’s public documents disagree on EIP-2935

The most important verification issue is in VeChain’s own repositories.

VIP-255 lists 11 Ethereum Improvement Proposals. Among them is EIP-2935, which makes recent historical block hashes available from state. The specification describes a VeChainThor implementation that would query the chain’s existing Extension builtin and return VeChainThor block IDs for the most recent 8,191 blocks.

But the public Thor Interstellar artifacts repository currently says EIP-2935 “has not been merged into” the release/interstellar branch. Its README says the designated history-storage address has no code until that merge occurs and calls its own feature table the full list in the meantime.

The VIP header also still labels the proposal “Draft,” while VeChain’s official communications say the all-stakeholder vote passed and the upgrade was green-lit. These are documentation-state conflicts, not evidence that the fork has been canceled or that EIP-2935 will definitely be absent at activation. They do mean developers should verify the tagged client release, genesis fork configuration and behavior on the official test environment rather than using the August specification as a deployment guarantee.

For most applications, the discrepancy will have no visible effect. It matters to contracts or tooling that expect EIP-2935’s history contract, its 8,191-block window or a specific result at address 0x0000F90827F1C53a10cb7A02335B175320002935.

What node operators and developers should check

VeChain’s official Interstellar overview says validators, public-node operators, exchanges, custodians and infrastructure providers must upgrade before activation. A node that continues enforcing the old rules after the fork can reject valid post-fork blocks and fall out of sync with the canonical network.

Operators should verify five things before block 25,902,540:

1. Client provenance: obtain the compatible Thor build from VeChain’s official repository or release channel, and verify the expected tag or checksum.
2. Fork configuration: confirm that the Interstellar activation block is present in the network configuration used by the node.
3. Synchronization: check that the node is caught up and has enough time to recover if a restart or resync is needed.
4. Application tests: run contract and RPC tests against the release actually being deployed, especially for new opcodes, precompiles and SELFDESTRUCT behavior.
5. EIP-2935 assumptions: directly test the history-storage address if an application depends on it.

Ported Ethereum contracts need extra attention because VeChainThor adapts several rules to its architecture. Transient storage is cleared after each clause, not merely after the whole multi-clause transaction. The “created in the same transaction” test for restricted SELFDESTRUCT behavior is likewise evaluated within a clause. Code that carries a lock or authorization value across clauses may behave differently than it does on Ethereum.

What does not change for VET and VTHO holders?

VeChain says Interstellar does not change VET or VTHO supply, VTHO issuance and burning rules, staking rewards, validator or delegator reward allocation, governance power, StarGate NFTs, existing wallet addresses or token contracts. No one should send assets to a third party for a supposed “Interstellar migration.”

That last point is also a scam filter. A legitimate protocol upgrade can create convincing phishing pretexts. Since VeChain says ordinary holders need take no action, any unsolicited message demanding a token swap, seed phrase, private key or wallet “synchronization” is inconsistent with the published plan.

Frequently asked questions

When will the VeChain Interstellar hardfork happen?

At block 25,902,540. VeChain estimated that block for September 16, 2026, at approximately 11:15:10 UTC, but the actual time depends on block production.

Do VET holders need to swap tokens?

No. VeChain says VET and VTHO holders do not need a migration, swap, new address or contract change.

Why is EIP-2935 unclear?

VIP-255 describes it as part of the upgrade, while the current Interstellar artifacts README says it has not been merged into the release branch. That may reflect documentation or implementation timing; developers should verify the final client behavior.

This article is for informational purposes only and does not constitute financial, legal or investment advice.