For EVM Developers Migrating to Hedera
PreviousUnderstanding Hedera's EVM Differences and CompatibilityNextAccounts, Signature Verification & Keys (ECDSA vs. ED25519)
Last updated
Last updated
Transitioning to Hedera’s EVM implementation offers exciting opportunities but also introduces unique challenges. As an EVM (Ethereum Virtual Machine) developer, you’ll find familiar Solidity smart contracts and EVM logic, but Hedera’s architecture, key management using ED25519, and enhanced capabilities such as system contracts introduced in HIP-632 necessitate adjustments to your workflows. This guide provides the insights and tools you need to migrate successfully.
This guide helps EVM developers understand key concepts and differences that impact how they deploy and manage contracts on Hedera:
Understand how Hedera’s account structure differs from the EVM, including ED25519 vs. ECDSA keys, dynamic key rotation, and how aliases enable compatibility.
Learn how to handle differences between the EVM standard 18 decimals and Hedera’s 8 decimals, ensuring accurate token calculations and conversions.
Discover strategies for designing secure smart contracts that accommodate key updates, enhancing account flexibility and security.
Explore explicit handling of HBAR transactions in Solidity contracts, enabling you to manage native token flows on Hedera.
Understand how Hedera’s JSON-RPC relay differs from the EVM RPC APIs, ensuring you can use familiar tooling with Hedera’s network.
