Ed25519
The Edwards-curve Digital Signature Algorithm over Curve25519, the default account scheme on a large share of chains launched since 2015. Broken by Shor's algorithm on a cryptographically relevant quantum computer, which recovers the private key from the public key.
- Quantum status
- Broken by Shor's algorithm
- Standard
- RFC 8032, final
- Family
- elliptic curve
- Also known as
- EdDSA, Curve25519
Rated chains using it
- AIOZ Network Mainnet, mandatory
Validator consensus. The consensus parameters accept ed25519 as the one validator key type, and all 50 validators in the latest set use it. Read on-chain
- Akash Network Mainnet, mandatory
Validator consensus. The consensus parameters accept ed25519 as the one validator key type, and all 80 validators in the latest set use it. Read on-chain
- Algorand Mainnet, default
Account signatures. Statement or write-up
- Aptos Mainnet, default
Account signatures. Specification or proposal
- Arweave Specified, not deployed
Account signatures. The node's wallet module can generate, sign and verify with Ed25519 keys, but its transaction validation accepts only RSA and ECDSA signature types, so Ed25519 cannot sign a mainnet transaction. Source code or release
- Beldex Mainnet, default
Account signatures. Spend and view keys on the Ed25519 curve, as on Monero: Beldex's documentation says a raw address is composed of two public keys, the public spend key and the public view key. Specification or proposal
- Beldex Mainnet, mandatory
Validator consensus. Master node keys: a Monero-style Curve25519 key pair for registration and votes, and a standard Ed25519 key pair for ancillary operations. Source code or release
- Cardano Mainnet, default
Account signatures. Statement or write-up
- Celestia Mainnet, mandatory
Validator consensus. Mainnet consensus parameters list ed25519 as the single allowed validator key type, as read on 22 October 2026. Read on-chain
- Cosmos Hub Mainnet, mandatory
Validator consensus. Used for consensus, never for transaction authentication. Specification or proposal
- Cronos Mainnet, mandatory
Validator consensus. Validator identities. Specification or proposal
- Decred Mainnet, opt-in
Account signatures. Signature type 1, verified by OP_CHECKSIGALT. Source code or release
- dYdX Chain Mainnet, mandatory
Validator consensus. The consensus parameters accept ed25519 as the one validator key type, and all 21 validators in the latest set use it. Read on-chain
- GateChain Mainnet, default
Account signatures. The one native account read, the vault account of consensus account GtNode-37, carries a gatechain/PubKeyEd25519 key; GateChain's wallet documentation says accounts use secp256k1. No ordinary native account with transactions was found to sample. Read on-chain
- Hedera Mainnet, default
Account signatures. Selectable per account, with ECDSA. Statement or write-up
- Injective Mainnet, mandatory
Validator consensus. Mainnet consensus parameters list ed25519 as the only validator key type; every bonded validator's consensus key read on 22 October 2026 was Ed25519. Read on-chain
- Internet Computer Mainnet, default
Account signatures. User identities sign with Ed25519 or ECDSA. Specification or proposal
- Internet Computer Mainnet, opt-in
Threshold signing. Chain-key signatures. Specification or proposal
- IOTA Mainnet, default
Account signatures. The default account scheme. Addresses are a BLAKE2b-256 hash of the key. Specification or proposal
- Midnight Mainnet, mandatory
Validator consensus. GRANDPA finality keys. Read at the node-1.0.400 release tag, which Midnight's release notes tell every Mainnet node to run; its runtime is spec version 1.0.300. Source code or release
- Monero Mainnet, default
Account signatures. Statement or write-up
- MultiversX Mainnet, mandatory
Account signatures. The node's transaction signer is Ed25519, and the developer documentation states that transactions are signed with Ed25519. Guardian co-signatures on guarded accounts use the same scheme. Source code or release
- NEAR Protocol Mainnet, default
Account signatures. Source code or release
- Polkadot Mainnet, mandatory
Validator consensus. Used in some consensus roles alongside sr25519. Specification or proposal
- Provenance Blockchain Mainnet, mandatory
Validator consensus. The consensus parameters accept ed25519 as the one validator key type. Read on-chain
- QoreChain Mainnet, mandatory
Validator consensus. Read on 23 October 2026: all eight bonded validators carry Ed25519 consensus keys. Read on-chain
- Sei Mainnet, mandatory
Validator consensus. All 40 active validators' consensus keys read tendermint/PubKeyEd25519 on mainnet. Read on-chain
- Solana Mainnet, default
Account signatures. Statement or write-up
- Stellar Mainnet, default
Account signatures. Statement or write-up
- Sui Mainnet, default
Account signatures. Statement or write-up
- Terra Classic Mainnet, mandatory
Validator consensus. The consensus parameters accept ed25519 as the one validator key type. Read on-chain
- Tezos Mainnet, default
Account signatures. tz1 addresses, the Octez default. Specification or proposal
- Tezos Mainnet, opt-in
Validator consensus. A baker's consensus key may be a tz1 key. Specification or proposal
- THORChain Mainnet, mandatory
Validator consensus. Mainnet consensus parameters list ed25519 as the one validator public key type. Read on-chain
- THORChain Mainnet, mandatory
Threshold signing. Threshold EdDSA for vaults on Ed25519 chains; the mainnet inbound address for Solana carries an Ed25519 vault key. Read on-chain
- TON Mainnet, default
Account signatures. Verified inside wallet smart contracts. Source code or release
- XRP Ledger Mainnet, default
Account signatures. Selectable per account, with secp256k1. Statement or write-up
Sources
- RFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA) , IETF. Accessed 19 October 2026.
Published beside the Hardy Score and not an input to it. How each chain is scored is set out in the methodology.