VeChain opens an EVM compatibility vote as Interstellar enters its next phase
VIP-255 would bring newer Ethereum execution and cryptographic features to VeChainThor, but the upgrade still needs stakeholder approval and an activation plan.
VeChain has opened the governance process for the next phase of its protocol roadmap. In a publication dated Aug. 6, the VeChain Foundation said VIP-255 would align VeChainThor with execution-layer changes from Ethereum's Cancun, Prague and Osaka upgrades. The vote is scheduled to run on VeVote from Aug. 10 at 00:00 UTC through Aug. 17 at 00:00 UTC.
Eligible validators and StarGate NFT holders can participate. The proposal is part of Interstellar, the third phase of VeChain's Renaissance roadmap, and its immediate question is whether the network's stakeholders accept the proposed compatibility package. The vote itself does not activate the software.
More of the Ethereum execution toolbox
VIP-255 lists a broad set of changes. They include transient storage for temporary contract state, MCOPY for memory copying, an updated SELFDESTRUCT behavior, a leading-zero-count instruction and safeguards around modular exponentiation. The proposal also includes BLS12-381 and secp256r1 support, which can help applications that rely on aggregate signatures, zero-knowledge systems or passkey-style cryptography.
Other items concern the chain's operating limits and developer visibility. Historical block information would become available through a standard EVM mechanism, a gas cap would set a ceiling on individual transactions and an 8 MiB execution-block limit would define a larger boundary for block processing. Together, the list is aimed at reducing the gap between VeChainThor and the tooling assumptions made by Ethereum developers.
The hard part comes after the vote
If the proposal passes, VeChain says the next steps will include a client release, node-upgrade instructions and a later announcement of the activation block. Validators, exchanges, custodians and infrastructure providers would need to upgrade before that block. This is the operational test for compatibility work: a specification only becomes a network change when the software and the organizations around it move together.
Ordinary VET and VTHO holders are not being asked to migrate tokens under the proposal. The immediate evidence to follow is the vote result, the client release and the behavior of applications during testing. Interstellar may give VeChain developers a more familiar execution surface, but adoption will depend on the quality of that rollout and on whether builders use the new capabilities.
