An ECDSA account can use the long-zero EVM address derived from its Hedera account ID.
This can work for addressing the account, but it isn’t the same as an EVM address cryptographically derived from the ECDSA public key.
25·CLong
T
Twitter9/3news
3�⃣ ECDSA (secp256k1) + derived EVM alias
For EVM-focused development, this is generally the preferred setup.
The 20-byte EVM address is derived from the public key and used as the account alias, giving developers an identity that works across Hedera native operations and EVM tooling.
65·B+Long
T
Twitter9/3news
1️⃣ ED25519
ED25519 works across Hedera’s native services and operations.
But there’s an important limitation for EVM development: ED25519 keys can’t natively function as standard EVM Externally Owned Accounts (EOAs) or work with mechanisms like ecrecover.
35·CShort
T
Twitter9/3news
The takeaway: 🔑
If you’re building EVM-compatible apps or smart contracts on @Hedera, ECDSA (secp256k1) with a derived EVM alias gives you the most straightforward path for interoperability with standard EVM tooling.
Want to go deeper? Watch https://www.youtube.com/watch?v=WvOr2jU5HVk
25·CLong
T
Twitter9/3news
ED25519 vs. ECDSA on @Hedera: what’s the difference, and when should you use each? 🔑
Both can authorize Hedera transactions, but your key choice also becomes an interoperability choice.
Here’s what developers should know 🧵 https://t.co/Y6snludVoU