The privacy problem sits in the settlement layer
The issue begins when Zcash liquidity moves through a cross-chain service. NEAR Intents supports bridging between blockchain networks, including a Zcash to Solana route, and publishes settlement information so that swaps can be completed or funds can be returned if a transaction fails. NEAR’s official bridging documentation describes the service’s cross-chain flow and its support for ZEC transfers.
That process creates a tension between private payments and transparent settlement. Zcash is designed to conceal transaction details from outside observers, but an interoperability service still needs an address or endpoint to send funds back to a user. If that information is recorded publicly, it can create a durable record linking the user to a particular swap.
The immediate exposure is not the same as losing control of funds. A viewing key can reveal payment history, while a spending key authorizes the movement of assets. The distinction matters because a person who obtains viewing access may be able to inspect transactions without being able to spend the associated ZEC.
The longer term concern is that cryptographic assumptions can change. Publicly exposed address information may be difficult to exploit with current computers, but a sufficiently powerful quantum computer could theoretically weaken the elliptic curve protections used by existing systems. If that happened, an attacker could potentially derive viewing information from a publicly recorded address.
Zcash wallets can also use multiple addresses connected to the same incoming viewing key. That structure means the compromise of one address may expose more than the history of one payment. It could provide a path to information about other received amounts and private memos associated with the same wallet.
One viewing key for each swap
The proposed response comes from Zakura, a software implementation of Zcash. Zakura engineer Adam Tucker proposed in the project’s engineering post deriving a separate incoming viewing key for every Zcash address published through NEAR Intents.
Under the design, each swap would have its own viewing boundary. A refund address linked to one failed or incomplete transaction would not automatically provide access to the wallet’s broader incoming payment history. If a future cryptographic break exposed that address, the information at risk would be limited to the individual swap tied to it.
The proposal preserves the wallet’s spending key with the user. That keeps the change focused on privacy segmentation rather than custody. The service would still be able to process the settlement flow, but the information associated with one transaction would be less useful for mapping the rest of a wallet’s activity.
This approach treats publicly recorded keys as long-lived liabilities. Even if no attacker can exploit them today, information placed on a transparent blockchain can remain available for later analysis. A privacy design therefore has to account not only for the current capabilities of computers, but also for the possibility that old records may be revisited after cryptographic standards change.
Recovery without revealing the search
Creating separate viewing keys introduces a practical problem. A wallet must still be able to identify where refunds landed, especially when a swap does not complete. Searching for every possible address through a public service could disclose more information about the wallet’s activity.
Zakura’s proposal addresses that issue with private information retrieval. The wallet can query a database for matching refund information without revealing which addresses it is looking for. In economic terms, that preserves the ability to reconcile funds without turning the recovery process into another source of metadata leakage.
That detail is important for cross-chain liquidity. A bridge or intent service does not simply move an asset from one ledger to another. It also manages failed transfers, routing instructions and settlement records. Each extra operational step can expose clues about who is moving money, where it is headed and which transactions belong to the same wallet.
Separating viewing keys reduces the value of any single piece of routing data. It does not make the public settlement layer invisible, but it narrows the consequences of a future compromise.
A wider interoperability challenge
L2BEAT’s privacy review of Zcash through NEAR Intents identifies risks in the existing arrangement, including public payout metadata, shared incoming viewing keys and operator visibility. The review also warns that a future cryptographic break could expose an account’s payment history.
That assessment represents the critical view identified for this story. No opposing assessment was provided in the supplied sources, so there is no basis to claim that the risks have been resolved or that the proposal has broad agreement.
The underlying question extends beyond Zcash. Privacy systems can maintain strong internal protections while losing information at the point where funds interact with bridges, intent-based swaps or other public coordination layers. Capital moving between networks needs settlement instructions, and those instructions can become a record of user activity even when the underlying payment protocol hides transaction details.
Zakura’s proposal responds by limiting how much history any one exposed address can reveal. Its success will depend on implementation, wallet compatibility and the ability of recovery systems to preserve privacy in practice. The larger lesson is that cross-chain liquidity requires more than confidential transfers. It also requires careful control over the metadata used to route, refund and reconcile them.
- coindesk.com · Link preview (og:image)
Ethan Brooks is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.
The models. Writing: gpt-5.6-luna. Out on the live web: gpt-5.6-luna and gpt-5.6-terra. Pictures: gpt-image-1. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.
How a story is made
- Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
- Writing. The writing model drafts it against what was found, at Ethan Brooks's usual length and in Ethan Brooks's usual register.
- The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
- Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
- Fact check. A last pass hunts for claims the article makes and its sources do not.
- A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.
If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.
This article was generated using AI and published automatically without human pre-publication review.
Read and checked by admin on 10/20/2026
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.