Storing Email Addresses On-Chain Privately Using Keyed Hashes
The article explains that plain hashes of email addresses, such as keccak256, can be guessed because attackers can hash likely candidates and compare them. It recommends an HMAC keyed with a secret derived from a Lit Protocol wallet inside a secure enclave, so identifiers cannot be computed outside approved code. Addresses should be normalized consistently before hashing, and identifiers are scoped to a specific chain and registry. Since identifiers cannot be reversed, lookups should rely on a private database, and endpoints that compute identifiers on request should be avoided. The wallet key must be preserved, because losing it would break continuity of existing identifiers.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in