The zk.money privacy wallet has returned as a way to make private payments connected to Ethereum, according to CoinDesk’s September 29, 2026 report. Payments within a privacy system can conceal details from public chain observers, but a deposit from an ordinary Ethereum address can still expose where funds came from, when they moved, and how much entered. Anyone trying the new release should verify its privacy claims and operational limits before relying on them.
The name is familiar because zk.money previously offered private Ethereum transactions and then disappeared from regular use. Its return raises a practical question for people who hold their own keys: where does the public history of their wallet stop, and where does the private payment begin?
What changed this week
On September 29, CoinDesk reported that zk.money had returned after roughly three years. That is the news: an Ethereum privacy payment option associated with Aztec is available again. The report establishes the relaunch, but it does not make every earlier feature, supported asset, or user experience a promise about this release.
The zk.money site is the place to check current access, supported networks, fees, and transaction flow before moving funds. Interfaces and limits can change quickly after a launch. For a self-custody user, the immediate relevance is that private payments may become a practical option again, while using them still creates public entry and exit points.
What does private mean here?
Public Ethereum transactions are visible by design. An observer can inspect a sender, a recipient, a value or token transfer, and a timestamp, then follow activity associated with those addresses. Ethereum’s transaction documentation explains the public transaction fields and the signatures that authorize them.
A zero knowledge payment system aims to validate a transaction without publishing every fact used to validate it. In a typical shielded design, encrypted records represent funds inside the system, and a proof shows that a transfer follows its rules. The Aztec documentation describes its privacy architecture; check the current zk.money documentation for the disclosure and withdrawal rules that apply to this release.
Privacy is therefore about a particular view of a transaction. A person watching Ethereum may see less about a payment made inside the privacy system than about a standard onchain transfer. The sender, recipient, amount, and payment history are not automatically hidden from every participant or every service involved.
| Stage | What an outside Ethereum observer may see | What may be concealed inside a private payment system |
|---|---|---|
| Deposit | Funding address, transaction time, contract interaction, and transferred value or token events | The eventual private recipient |
| Internal payment | Public proof or settlement activity, depending on the design | The private sender, recipient, or payment amount, subject to the product’s actual rules |
| Withdrawal | Destination address, time, and released amount or asset | Earlier internal transfers, if other clues do not link them |
This table describes the privacy boundary, not a verified feature list for every payment route. Some details depend on which assets and transaction types the current app supports. Even when cryptography hides internal records, public entry and exit transactions remain valuable clues.
What a wallet deposit can reveal
Depositing from a self-custody wallet generally requires a public Ethereum transaction. A block explorer can show that the address interacted with a contract at a particular time. If the deposit transfers ETH or a public token, its value or token transfer event can also be visible; the Ethereum account model makes address histories easy to inspect.
That matters because an address can be connected to its owner outside the chain. You might have used it with a public profile, an exchange withdrawal, a donation, or an app that knows your identity. A private payment made afterward does not erase that earlier association. If there are few deposits of a given size at a given time, matching a later withdrawal may become easier, even without breaking the proof system.
There can be a second visible action before a token deposit: an approval allowing a contract to spend the token. Whether zk.money asks for one depends on its current flow and asset. Read the wallet prompt, inspect the spender address against the official interface, and grant only the access needed where the interface permits. An unlimited approval can remain a separate wallet risk after the payment.
You may also reveal information to services that help you reach the app. A website, RPC provider, or network provider can observe metadata such as an IP address or the moment you request data. Cryptographic privacy onchain does not by itself prevent those observations.
Can a private payment be traced back to you?
The answer depends on the full path of funds. A shielded transfer may hide the direct relationship between participants from ordinary chain observers, but a deposit and withdrawal can still be correlated through timing, unusual amounts, asset choice, or a small pool of activity. Sending funds out and immediately spending them from the recipient’s public address may create another link.
The person receiving a payment may also learn who sent it from an invoice, a message, or a shared transaction reference. An exchange or other service can have records of funds entering or leaving its platform. Privacy software changes what strangers can learn from the ledger; it does not delete information already held by counterparties.
Consider a hypothetical deposit of a distinctive amount followed soon afterward by a withdrawal of a similar amount to a known address. That pattern could invite a guess even if the internal transfer is cryptographically sound. It is a correlation risk, not proof that an observer can read hidden transaction data.
What are the risks of an early release?
New software can change quickly, and a privacy payment app adds several layers beyond ordinary wallet sending. A user may need to trust a website to display the right contract, a wallet to describe a signature, contracts to hold or move funds correctly, and infrastructure to submit or prove transactions. A failure at any layer can affect access to funds or the privacy the user expected.
Check the current documentation for the way deposits are controlled, how withdrawals work, and what happens if the interface is unavailable. Ask whether a payment can be reversed, whether it needs a separate withdrawal step, and how long each step is expected to take. A successful deposit alone does not show that an eventual withdrawal will be simple.
Privacy protections also depend on actual usage. A system with little activity offers fewer other transactions to blend with, and a rare asset or conspicuous amount can stand out. Neither a large user count nor a specific anonymity guarantee should be assumed without current, measurable evidence.
Finally, watch for impersonation. A relaunch creates an opening for fake sites and support accounts. Start from a verified official link, bookmark it, and do not enter a seed phrase into a website. A privacy tool cannot protect funds from a malicious signature or a stolen key; our guide to wallet approvals and contract permissions explains why these prompts matter.
A practical checklist before depositing
- Confirm the live URL and contract details through zk.money’s current official channels. Do not rely on a search ad or a direct message.
- Read the specific asset, network, deposit, payment, and withdrawal instructions for the current release. Older zk.money guides may describe a different product.
- Check each wallet prompt for the asset, destination or spender, amount, and permission scope. Stop if the prompt differs from what you intended.
- Make a small test deposit and complete a test withdrawal before moving an amount that matters to you. Record transaction IDs so you can reconstruct the public steps.
- Decide what privacy you need: hiding payment details from casual chain observers differs from hiding your identity from a recipient, an exchange, or a service provider.
The related guide to receiving crypto safely covers address checks that still apply when funds return to a public wallet. Keep records of deposits, internal activity that the app lets you export, and withdrawals. You may need them to understand balances, resolve a support issue, or meet your own reporting obligations.
The self-custody takeaway
The September 29 relaunch gives Ethereum wallet users another way to explore private payments after a roughly three-year gap. Its useful promise is narrower than invisibility: shielded activity can reduce what the public ledger exposes about payments, while wallet deposits, withdrawals, metadata, and human context can still disclose a great deal.
Treat the first transfer as an exercise in understanding that boundary. Verify the current product details, read every approval, and test the complete route from deposit through withdrawal before relying on it for a real payment.
