Stealth addresses: private receiving, with caveats
A stealth-address scheme creates fresh receiving destinations from a recipient’s shared meta-address. This can reduce links between payments, but amounts, timing, fee funding, and later spending may still reveal relationships.
Follow the receiving process
A fresh destination does one specific job
A meta-address is information a recipient shares so a sender can create a fresh receiving address. The recipient uses their keys to find and control the payment. This can reduce the need to reuse one public destination. It does not make the amount or every later transfer disappear.
- Sender: Uses the scheme to create a destination for the recipient.
- Recipient: Scans for payments using the required keys and software.
- Later spending: Can create new links through timing, funding, or transfers.
Keep in mind: Check how the tool restores access and pays spending fees before relying on it.
Work through receipt, discovery, and spending
Receipt and discovery are separate steps
A sender can create a fresh destination, but the recipient still needs software that recognizes the payment and the keys required by the scheme. A balance being visible on an explorer does not establish that a particular backup can restore spending access. Read the implementation’s scanning and recovery instructions together.
Include the later payment in the privacy question
Receiving at a fresh address is only one stage. Ask how the account gets the gas needed to spend, and where the funds go next. A later transfer can reveal a relationship that the receiving step did not. Compare that remaining exposure with your threat model before treating the feature as a solution to a broader identity problem.
How does a stealth receiving address work?
A stealth-address scheme can derive a different destination for a payment using a recipient’s published meta-address and data used by the scheme’s math. This reduces the need to publish one address for all incoming payments. The recipient scans for payments they can control instead of asking every sender to reuse one destination.
What information can still reveal a link?
The payment still occurs on a ledger. Amounts, timing, gas funding, and later movements may reveal relationships. A scheme that improves separation between a recipient and their payments does not necessarily conceal the sender or the payment amount. The implementation’s assumptions matter as much as the headline feature.
Recovery and usability are part of security
The recipient needs the right keys and scanning process to discover and spend funds. Before using a system, understand backup and restoration, supported networks, and how it handles the fees needed to move received assets. Sending meaningful funds before understanding recovery creates avoidable risk.
Read the standard and the product separately
ERC-5564 specifies a stealth-address mechanism, not a blanket guarantee about every application using the idea. Evaluate the actual implementation, operational metadata, and audit scope. Start with conceptual understanding and documented limitations rather than accepting a claim of complete anonymity.
Check the source
Ethereum Improvement Proposals
This is an original, AI-assisted educational explanation. Sources and limitations are provided for verification; it is not personalized financial advice. Read the editorial policy or report a correction.
