hashgraph
EVM Address: Terminology and Recommended Usage
Accounts, Keys, and EVM Addresses
We need to update all relevant pages that touch on Accounts/Properties/EVM address to reflect the following information:
Terminology
Every Hedera account has an EVM address, which can be derived from either: • The account’s public key, or • The account’s ID
This terminology aligns with what Ethereum developers are already familiar with. The Hedera Mirror Node REST API already exposes this as the evm_address field in the /accounts endpoint.
Note: • When derived from the public key, the EVM address is a standard EVM address (computed as the last 20 bytes of the Keccak-256 hash of the public key). • When derived from the account ID, the EVM address is a hexadecimal representation of that account ID.
Recommended Usage
To maximize EVM compatibility, the recommended default approach is to: 1. Create accounts with ECDSA keys 2. Set the account alias to the EVM address derived from the public key
This ensures that accounts can interact seamlessly with EVM-based tools, wallets, and smart contracts.
Note: If your use case requires key rotation, avoid this default approach. Instead, use an account structure that supports key changes, as EVM-address-based aliases are tied to the original public key.
@theekrystallee
