Build with ERC-5564

Stealth payments are an open standard. Any wallet can add them, and every wallet that does makes the crowd bigger for everyone. This is the short list of what it takes, and what we learned doing it.

The piecesCopy Anchor Link

SendingCopy Anchor Link

1. Get the receiver's meta-address: pasted, or from the ERC-6538 registry for an address or ENS name.
2. Generate the one-time address and the ephemeral key.
3. Announce first, then pay. If the payment fails after the announcement, nothing is lost. The other order can leave funds where the receiver cannot find them.
4. Put the view tag in the first byte of the metadata. Use the standard layout so every client can show what was paid.

ReceivingCopy Anchor Link

1. Derive keys from one signature, and check determinism: sign twice and compare. Some wallets cannot recreate the same signature, and keys they produce are keys their users will lose.
2. Scan on the device. The view tag removes 255 of 256 strangers' payments before any curve multiplication that matters.
3. Treat announcements as claims to verify. Anyone can announce anything.

Withdrawing: the part that decides privacyCopy Anchor Link

Our leak study found that the math holds and the habits leak. If you ship one thing, ship these defaults:

• never offer the wallet the keys come from (or the registrant) as a destination (H1);
• no sweep-all: one payment, one path, one time (H3);
• network-standard fees only (H4);
• warn on round trips to the payer (H2) and on fast withdrawals.

Our client implements these as plain functions you can copy; see Receiving.

QuestionsCopy Anchor Link

Write to devs@ephemeral.money. We answer builders first.