0x1b08ed4f1b08…1b08ed4c
Ethereum Stealth Group Plans Post-Quantum ERC-5564 Work
A planned Ethereum stealth-address group will meet every two weeks to pursue hybrid ML-KEM for ERC-5564, mainnet key rotation and hardware-wallet support.

Outputs
The planned engineering group will meet every two weeks.
Post-quantum security is among the group's stated priorities.
Hybrid ML-KEM is proposed for ERC-5564 alongside a separate independent implementation.
A singleton Ethereum mainnet key store would support key rotation and metadata management.
Listed participants include the Ethereum Foundation, ScopeLift, the Umbra team, Fluidkey and Trezor.
By Daniel Okafor
A planned Ethereum stealth-address engineering group will meet every two weeks, with hybrid ML-KEM work for ERC-5564 and a separate implementation effort forming the core of its agenda.
The initiative comes from Pierre, an Ethereum Foundation privacy contributor, who plans to convene engineering teams to address the cryptographic and usability challenges surrounding Ethereum stealth addresses. Post-quantum security is among the group's stated priorities.
The proposal provides no kickoff date, budget, charter or implementation deadline. It therefore describes a planned engineering program, not a completed standards process or a deployed privacy stack.
What does the ERC-5564 work involve?
Pierre's proposal lists a "hybrid ML-KEM approach" for ERC-5564 as one technical strand. A second strand would proceed as an independent implementation intended to move the standard toward final status.
The two-track structure separates a cryptographic approach from implementation work. It also means hybrid ML-KEM is not presented as the only route toward finalization, although the source gives no cipher suite, client specification or delivery schedule.
The stated objective is narrower than a wholesale Ethereum privacy upgrade. The work concentrates on stealth-address cryptography and the practical steps needed to carry that functionality toward an established standard.
How would the mainnet key store work?
The agenda calls for a "singleton key store" on Ethereum mainnet to support key rotation and metadata management. That gives the proposal a defined network target and two operational functions for the proposed component.
Key rotation is the store's stated support function, while metadata management covers information associated with those keys. The source does not define the store's architecture, custody model or interface, so those operational choices remain open.
If applications are to rely on a singleton location, the group will need common rules for key changes, metadata updates and wallet access. The proposal does not say whether those rules have been drafted or assigned to a particular participant.
What does wallet integration add?
Hardware-wallet integration is another listed workstream. The agenda does not name supported devices, but it places hardware-wallet support alongside the key store rather than treating stealth-address use as software-only.
Standardized key-storage practices and wider adoption complete the stated scope. Together, those tasks would determine whether the work can move beyond a cryptographic specification into repeatable wallet workflows and broader use.
Who is involved?
Listed participants are the Ethereum Foundation, ScopeLift, the team behind Umbra, privacy wallet Fluidkey and hardware-wallet maker Trezor. The roster links the foundation with projects connected to stealth addresses, privacy software and hardware-based key storage.
Fluidkey is identified specifically as a privacy wallet, Trezor as a hardware-wallet maker and Umbra through the team behind it. The source gives no separate role for ScopeLift beyond its inclusion in the participant list.
That mix gives the biweekly group several implementation perspectives, but it does not establish who will own each deliverable. The proposal names no maintainer assignments, decision rules or release authority.
What should readers watch?
The source sets no release date or adoption target for ERC-5564, the singleton key store or hardware-wallet support. It also does not identify a standard for judging whether the independent implementation is ready for final status.
The two-week meeting schedule is the clearest operating commitment. It creates a recurring forum for resolving specifications and assigning work, but the agenda alone does not show whether those discussions have produced code or a deployment plan.
Any change to Ethereum's key-management structure still depends on a specified ERC-5564 implementation, a deployable mainnet key store and working hardware-wallet integration. Until those pieces exist, the proposal changes the engineering agenda, not the standard's status.
via tokenpost.com (Source)
More from Daniel Okafor
Show full bio
Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.
1,514 articles