A NeoVM-compatible RISC-V digital machine resolution for Neo 4 has handed block-by-block state root verification in opposition to the complete Neo MainNet dataset, confirming the design has moved past the conceptual stage. Neo co-founder and core developer Erik Zhang shared the milestone, describing the consequence as validation that the method produces an identical state transitions to the present system.
The achievement follows Zhang’s draft Neo 4 roadmap printed in Sept. 2025, which proposed NeoVM 2 as a next-generation digital machine with RISC-V compatibility, fine-grained fuel metering, and improved value effectivity. On the time, Zhang acknowledged that adoption of RISC-V would permit Neo to onboard current developer infrastructure, enhance effectivity, and improve help for zero-knowledge proofs.
Structure and validation
The implementation integrates PolkaVM, a RISC-V-based digital machine initially developed by Parity Applied sciences for the Polkadot ecosystem, into Neo’s execution setting. An structure diagram shared by Neo core developer Jimmy Liao illustrates the layered design: the Neo Core C# node interfaces with a PolkaVM Host Runtime written in Rust by way of a International Perform Interface bridge, with a RISC-V sandbox layer supporting each legacy NeoVM bytecode and native RISC-V contracts.
The NeoVM-compatible RISC-V VM resolution has been accomplished. State root-level verification handed for each block on the mainnet information. Nonetheless an exploratory work. pic.twitter.com/GY2RKjU9U1
— jimmy.neo (@r3ejimmy) April 11, 2026
State root verification works by evaluating the cryptographic hash representing the blockchain’s total state at every block peak. By working the brand new VM implementation in opposition to each MainNet block and confirming matching state roots all through, the group demonstrated practical equivalence between the RISC-V-based system and the present NeoVM.
Two paths for Neo’s future
Zhang acknowledged that the validated resolution opens two paths for Neo’s growth: preserving compatibility with the present NeoVM contract ecosystem, and creating room for native RISC-V contract execution. He mentioned:
“That is nonetheless exploratory work, however the route is now clear: develop Neo’s VM capabilities and developer prospects with out fragmenting the present ecosystem.”
The twin-path method aligns with the broader Neo 4 design philosophy, which emphasizes full backward compatibility to make sure current tokens, good contracts, and functions deployed on Neo N3 proceed to perform with out migration or redeployment.
RISC-V is an open-source instruction set structure that permits good contracts to be compiled to a normal instruction set reasonably than customized bytecode, probably broadening language and tooling help. Different blockchain tasks, together with Ethereum, have explored RISC-V as a complement or substitute for current VM architectures.
Zhang’s unique announcement might be discovered on the hyperlink beneath:
https://x.com/erikzhang/standing/2042992425145160183
