Injective Introduces Native EVM, What's Next? – Populus

# Key Takeaways Injective Labs announced the launch of the Injective EVM in January 2025. This decision is seen as a move to broaden its developer ecosystem by integrating it directly into the core of Injective, rather than relying on separate off-chain computation. However, this does not mean abandoning the existing WASM smart contracts. Instead, it is part of a multi-VM strategy aimed at removing barriers for developers onboarding to Injective. Should the adoption of EVM successfully expand its developer ecosystem, Injective might consider integrating other VMs like the rapidly growing MoveVM or SVM, which leverages the vast Solana ecosystem. The impact of Injective’s native EVM on its future ecosystem growth remains to be seen. # Background – Introduction of Injective’s Native EVM and Its Reasons ## Why EVM? Injective Labs, a key contributor to the Injective network, announced the integration of a native EVM execution environment into the core of the Injective chain in January 2025. The primary reason for this integration is to leverage Ethereum's extensive developer community and its mature tooling environment. While Injective has seen success through innovative technology integrations and aggressive business expansions, attracting developers specific to Injective has been a challenge. The need to improve the developer environment, therefore, played a significant role in the decision to adopt a native EVM. Statistics support this move. According to a developer report by Electric Capital, around 74% of developers working on multi-chain platforms develop on EVM chains. Ethereum continues to lead in developer activity across all continents, indicating that Solidity-using EVM developers still dominate the blockchain industry. Chains that do not support EVM incur significant costs and time in creating and attracting a developer ecosystem. In contrast, chains supporting EVM can more easily attract developers familiar with blockchain, enhancing productivity without additional technical learning barriers. Many developers requested the integration of an EVM environment during the onboarding process at Injective Labs. Given that Layer 1's direct customers should be developers rather than users, listening to and implementing developer requests is crucial. Great builders will ultimately attract users. ## Injective EVM Deep Dive ### Not Just EVM but Multi-VM Before delving deeper into Injective's native EVM, it should be clarified that Injective still implements WASM contracts. This is not a pivot to EVM but a strategy to maintain the existing WASM environment while integrating EVM. The EVM is implemented in the core of the chain, creating a seamless execution environment while coexisting with the WASM-based environment. Moreover, it uses the latest Geth (Go-Ethereum) Ethereum client EVM implementation, ensuring compatibility with Ethereum's latest tooling and standards. ### Atomicity of Transactions Ensuring transaction atomicity is crucial, particularly when sequential transactions are required to achieve a desired outcome. A single transaction failure can result in not achieving the desired outcome, causing unnecessary transaction costs or asset losses. In a guaranteed atomic environment, failing transactions roll back the entire transaction sequence, maintaining consistent system state. Injective ensures data integrity and consistency by allowing multi-message transactions to roll back if a step fails. This atomic transaction feature is vital for a finance-focused blockchain like Injective. ### Module Compatibility Injective is distinguished by its modules that simplify application development. With the EVM update, EVM developers can use Injective’s inherent modules, leveraging features like CLOB, batch auctions (FBA), and shared liquidity environments to implement various financial applications. ### AI-Ready VM Injective’s EVM allows on-chain execution of AI inference, facilitating various AI and blockchain initiatives. This reduces reliance on off-chain computation, enabling the use of AI in portfolio management, financial data analysis, and managing organizational assets like DAOs more effectively. Before the native EVM integration, Injective had various AI-related initiatives and partnerships, benefiting EVM developers. ### Multi-VM but Single Token Despite supporting multiple VMs, Injective ensures token standardization using the Bank Precompile and ERC20 Module. These solutions facilitate smooth on-chain management and synchronization of token activities across WASM and EVM environments, ensuring consistency and preventing double accounting issues. They enable native asset mapping to ERC-20 standards, increasing development flexibility and broad ecosystem support. # Implications – What’s Next After EVM Implementation? ## Injective Remains One of the Fastest Blockchains Injective has consistently demonstrated exceptional performance. Performance tests of the Injective EVM in real network environments achieved approximately 4,500 TPS, and up to 12,500 TPS in ideal conditions, outperforming other high-performance EVMs. Maintaining compatibility with the latest Geth, Injective matches the technical capabilities of other EVM chains. So, what does Injective need next? ## Attracting Developers Following the EVM integration, Injective must attract excellent EVM developers. With numerous choices available to developers, Injective must offer appropriate incentives and engage in hackathons and long-term communication with developer communities. Injective’s loyal community (Ninjas) is an advantage, providing potential users for applications built by developers. Actively promoting Injective's native EVM to builders is essential. ## Beyond EVM: Embracing Multiple VMs Injective’s multi-VM ecosystem aims beyond EVM adoption. It has experimented with building in the SVM ecosystem and partnered with Solana’s Sonic. Depending on ecosystem growth, Injective may natively support other VMs in the future. The ability to integrate diverse developer ecosystems into a single core will be essential. Ultimately, smart contract platforms must cater to builders, not just users. Providing an environment where developers can easily create is crucial for all smart contract platforms. Given Injective’s current direction, it seems promising. Will we see Injective SVM or Injective MoveVM? ## Conclusion: The Time for Injective Is Now Various EVM chains continue to emerge, each attracting developers and users with unique characteristics. Nonetheless, Injective boasts significant value propositions. Injective has successfully operated without network issues for the past four years, appealing to institutions valuing network stability and consistency. Supporting both EVM and WASM differentiates it from other "fast EVMs." Additionally, unique features like its burn-based tokenomics and robust performance can attract developers and users. Now seems to be the optimal time for Injective to realize its potential. Can Injective capitalize on its achievements over the past four years?