KEY TAKEAWAYS
- Telos Core Developers have successfully deployed Telos EVM version 2.0, enhancing network features and minimizing install footprint.
- The upgrade introduces technical enhancements, though EIP-1559 fee market changes are still under development.
- Partners are advised to transition to version 2.0 to avoid service disruptions, with phased discontinuation of older versions.
- Node operators can access resources and support for running their own Telos EVM nodes via GitHub and the Telos Developer Community.
Telos Core Developers have announced the successful deployment of Telos EVM version 2.0, effective November 20, 2024. This upgrade aims to bring the Telos network closer to feature parity with Ethereum while minimizing the install footprint. The new version is accessible via the Mainnet at rpc.telos.net and the Testnet at rpc.testnet.telos.net.
Technical Considerations and Features
The Telos EVM 2.0 introduces several technical enhancements. Notably, the fee market change from the Ethereum London hard fork (EIP-1559) is still under development and not yet supported. However, long-running multicall (eth_call) read-only operations will no longer time out, although long-running transactions remain constrained and should be batched.
Solidity version compatibility remains unchanged, with version 0.8.23 fully supported and version 0.8.24 partially supported. More details on these updates can be found here.
Transitioning to Version 2.0
To modernize the infrastructure, Telos will discontinue support for EVM versions 1.0 and 1.5 in phases. Partners are advised to prepare for this transition to avoid service disruptions. The new version introduces a revised block hash calculation methodology. Partners not relying on block hashes can migrate seamlessly, while those dependent on block hashes, such as exchanges and indexers, may need to re-index the chain. Importantly, transaction hashes remain unchanged.
Starting January 6, 2025, Telos will implement rate-limiting on all hosted 1.x RPC infrastructure, initially capping requests at 50 per second. Further reductions will follow to encourage migration to version 2.0. The Mainnet RPC endpoints that will no longer be supported include mainnet.telos.net/evm, mainnet15.telos.net/evm, mainnet-us.telos.net/evm, mainnet-eu.telos.net/evm, and mainnet-asia.telos.net/evm.
Resources for Node Operators
Node operators interested in running their own Telos EVM node can access detailed resources, including an installer script and documentation, available on the GitHub repository. Support is also provided through the Telos Developer Community.
Telos Core Developers strongly encourage all partners to begin migrating to Telos EVM 2.0 to take advantage of its enhanced capabilities and ensure uninterrupted service.
Explore More News:
Disclaimer: The views expressed in this article are those of the authors and do not necessarily reflect the official policy of CoinsHolder. Content, including that generated with the help of AI, is for informational purposes only and is not intended as legal, financial, or professional advice. Readers should do their research before taking any actions related to the company and carry full responsibility for their decisions.
