Decentradge
Menu

Ethereum stealth-address group outlines work on ERC-5564, key registry and hardware wallets

In a report published on November 18, 2026, at 21:30 UTC+8, TechFlow said Pierre, a member of the Ethereum Foundation’s privacy research effort, had announced a working group focused on stealth addresses. The reported participants include the Ethereum Foundation, Umbra developer ScopeLift, stealth-address wallet Fluidkey and hardware-wallet maker Trezor. The group plans to meet every two weeks.

The work is focused on Ethereum privacy infrastructure, not a cross-chain bridge. Its proposals concern how recipients register stealth-address information, how wallets handle the associated keys and how ERC-5564 could advance as a standard.

One proposal would add a hybrid ML-KEM approach to ERC-5564, combining existing elliptic-curve cryptography with lattice-based cryptography to address a potential future risk of tracing historical transfers with quantum computers. The group also plans a separate production-grade reference implementation. According to the report, two independent reference implementations and a system-level code audit are prerequisites for moving ERC-5564 to Final status.

Ethereum stealth-address group outlines work on ERC-5564, key registry and hardware wallets

For users who receive funds through multiple applications, the group proposes a singleton key registry on Ethereum mainnet. It is intended to provide a common interface for registering and resolving stealth meta-address information, including separate spending- and viewing-key permissions, key rotation and encrypted metadata indexing. The report describes this as planned work, not a deployed mainnet contract.

The group is also working with Trezor on firmware-level key derivation and signing support for stealth addresses, along with proposed standards for derivation paths and viewing-key export. These are integration goals, not confirmed capabilities of current devices. The reported next steps include cross-auditing the reference code, deploying the registry to a testnet and testing hardware-wallet signing interfaces.

Further reading