A working group is taking shape around a practical question for Ethereum privacy: how can people receive funds through stealth addresses while managing their keys across apps and hardware wallets? In a report published on November 18, 2026, TechFlow said Pierre, described as a privacy researcher associated with the Ethereum Foundation’s ecosystem portal, had announced the group’s formation.
According to the report, the group’s website names the Ethereum Foundation, Umbra core development team ScopeLift, stealth-address wallet Fluidkey and hardware-wallet maker Trezor among its participants. It says the group plans to meet every two weeks. The work described remains a set of engineering goals, not a completed rollout.
The technical work has four parts:

- ERC-5564 and quantum resistance. The group proposes a hybrid ML-KEM approach combining existing elliptic-curve cryptography with lattice-based cryptography. Its stated aim is to protect historical transfer records against future quantum-assisted tracing. The report also says the group is working on a separate, production-grade reference implementation. It describes two independent reference implementations and a system-level audit as prerequisites for moving ERC-5564 to Final status.
- A shared key registry. A proposed singleton contract on Ethereum mainnet would give compatible apps a common way to register and resolve stealth-address metadata. The design aims to separate spending-key and viewing-key permissions, support key rotation and index encrypted metadata, rather than require users to publish a stealth meta-address in each app.
- Hardware-wallet support. The group and Trezor plan to work on firmware-level key derivation and signing, along with common derivation paths and a viewing-key export standard. Offline shared-key calculation, transfer scanning and signing are described as intended capabilities, not features confirmed to be available today.
- Testing and integration. The reported next steps include cross-auditing the reference implementations, deploying the proposed registry on a testnet and testing hardware-wallet signing interfaces. A planned testnet deployment should not be mistaken for a live mainnet registry.
For early adopters, the distinction is important: the report maps a route toward easier non-custodial private receiving, but does not establish that the standards, registry or Trezor integration are finished.


