Welcome to the next crypto level
← Nexorena

Sécurité

Draft Ethereum standard aims to restore post-quantum keys across wallets

Opened for discussion on November 13, ERC-8499 proposes a common way to derive signing keys from a BIP-39 recovery phrase. The draft distinguishes keys that can be restored from keys whose use has to be tracked.

Nexorena Editorial Team

Draft Ethereum standard aims to restore post-quantum keys across wallets

The same phrase can produce different keys in different wallets

On November 13, 2026, Johann Barbie presented draft standard ERC-8499 for deriving hash-based signing keys from a BIP-39 recovery phrase. The phrase, optionally paired with a separate passphrase, lets a wallet reconstruct a starting value. The author lists several implementations that use the same backup but apply different methods. Restoring the same words in two programs can therefore produce incompatible keys. The draft aims to define the common steps needed to recover the same keys in compatible wallets.

The draft addresses key derivation, the calculation that links keys to the backup. It draws on hash-based signature schemes that Ethereum accounts can already verify through their own contracts. The draft neither changes the protocol to require those signatures nor moves existing accounts to a new way of signing. It describes what wallets that adopt the proposal would need to implement.

Derivation would avoid elliptic-curve keys

The draft proposes calculating a root from the BIP-39 seed and deriving a distinct value for each account and key type. It uses functions based on HMAC-SHA512 and avoids the BIP-32 key tree, which uses elliptic-curve operations. The draft says this separation aims to prevent a quantum compromise of a conventional key from the same phrase from exposing the new hash-based keys.

The draft’s core defines, among others, the SLH-DSA key types standardized in FIPS 205. Two wallets applying the same rules with the same phrase and passphrase, where applicable, could produce the same key pair for a given account and key type. A different type identifies a different scheme or parameter set and yields a different key. The draft also calls for displaying a key fingerprint to help spot a typing mistake during recovery.

Some keys require a backup of their state

For keys whose state changes after use, including those in some one-time signature schemes, the draft follows a different rule. The phrase alone would not recreate an existing instance. The wallet would use a random value for each instance and store it with the key’s state. Restoring an old state could cause a key designed for one use to sign a second time.

The text is available as a pull request in the Ethereum standards repository. The author is seeking feedback and provides test vectors and a reference implementation to compare results. The proposal remains a draft. Recovery across wallets would depend on both wallets adopting the same rules and supporting the same key types.

Written with love byRyan MitchellMeet this editorial pen name ↗

Explorer Nexorena