Withdraw without leaking
The cryptography of a stealth address holds. What breaks privacy is the next move. The five habits behind most traces, and what the client does about each.
In our mainnet scan of 25,688 stealth addresses, 38.92% of the 25,057 that were withdrawn were traced to their owner. Almost every trace came from a habit after the payment, not from a weakness in the math. The client makes the safe path the default one.
The five habits
| Leak | What gives you away | In our data | Default in ephemeral |
|---|---|---|---|
| H1 registrant reuse | Withdrawing to the address that registered your stealth keys | 9,711 traced single withdrawals | That address is never offered as a destination. Typing it in shows a hard warning. |
| H2 round trip | Sending funds back to the address that paid you | 426 traced single withdrawals | Blocked: the payer is never a destination, and Withdraw stays locked until the payer is known. |
| H3 collector | Sweeping many stealth addresses into one wallet | 45.77% of single withdrawals, in 3,793 clusters | No sweep-all button. Each payment moves on its own path, at its own time. |
| H4 fee fingerprint | A custom priority fee that repeats across withdrawals | 1,031 stealth addresses in 465 groups | Fees follow the network's standard values. |
| H5 gas funding | Sending ETH from your main wallet so a token-only stealth address can pay gas | 0 of the 3 token-only addresses that paid their own gas | Never funded from a linked wallet: a token payment whose ETH for gas came from one is blocked. Sponsored gas is on the roadmap. |
H1 and H2 name you directly. H3 and H4 do not name anyone, but they group your payments together, so one mistake anywhere links all of them.
What still links payments
No default makes you invisible. These are on you:
- Timing. A stealth address that receives funds and moves them a minute later is easy to pair with the payment. Wait.
- Amounts. 1.2345 ETH in and 1.2345 ETH out is a fingerprint. Split and round where you can.
- Destinations you reuse. If every payment ends up in the same exchange account, the exchange can group them, and so can anyone it shares data with.
- Your own words. Posting a stealth address, or the transaction that paid it, undoes the work.
A safe withdrawal, step by step
Pick one payment. Move it on its own, not together with others.
Pick a destination that has never touched your public address. A fresh address, another stealth address, or a shielded pool.
Let the client set the fee. Do not set a custom priority fee.
Wait, and avoid exact amounts. The longer and less exact, the weaker any timing or amount link.
Gas
A stealth address that received only a token has no ETH to pay gas. Funding it from your main wallet is H5. Until sponsored gas ships, the client tells you which payments need gas and never offers to fund them from a linked wallet. The option today: receive a little ETH to the same stealth address as part of the payment. A relayer and gas tank, so a stealth address never needs ETH from your main wallet, is planned and not live yet (roadmap). If a token still leaves through someone else's relayer, the collector check (H3) counts that transfer like any other withdrawal, and when it cannot read it, H3 says the history is incomplete instead of calling a destination unused.
Non-standard tokens count as incomplete history: Withdraw stays off for a token address with no contract, and for a token whose arrival left no standard Transfer log the client warns that withdrawing it may link payments, and H3 never calls a destination unused.
Stay unlinked.