Zcash software developer Zakura has proposed giving each Zcash swap routed through NEAR Intents its own viewing key, an attempt to limit how much transaction history a future attacker could link together. The proposal targets refund addresses that become publicly visible when shielded ZEC moves through NEAR Intents. It hasn't been adopted anywhere yet, and Zakura's proposal is still under review.
Where cross-chain swaps leak
Zcash's privacy model depends on shielding transaction details. Cross-chain swaps don't fit neatly into that model. Moving shielded ZEC through NEAR Intents creates points where information can become public, and the refund address is one of them. A publicly visible address can be tied back to a wallet's viewing-key structure. That's the gap Zakura is trying to close.
The design: one key per swap
Under the proposal, every swap would get its own viewing key. Spending authority stays with the user. If a viewing key ends up compromised, it would expose information about a single swap rather than a wallet's entire past transaction history. The proposal also contemplates private information retrieval, which would let software find relevant refunds without broadcasting which addresses a user is checking.
The aim is to shrink the blast radius. One key, one swap. Not one key, every trade a user has ever made.
Preventative, not reactive
This isn't a response to a demonstrated quantum attack against Zcash. Zakura frames it as preventative engineering against a risk that could emerge if cryptographic advances make viewing-key relationships exploitable. That framing matters: there's no active incident here, and no evidence that anyone has linked wallets this way.
But the proposal assumes the risk is real enough to design around now. The point is to make sure that if the assumption someday becomes a problem, the available history to link is smaller than it would be otherwise.
Nothing is live yet
The proposal is a proposal. It remains under review. Supporters haven't delivered a widely deployed solution, and protection would still need to be implemented, audited, and adopted by wallets before it does anything for ordinary users. That's a long chain, and each link can stall.
So for now, Zcash users swapping through NEAR Intents are operating on the model that exists today, not the one Zakura is sketching. The next thing to watch is whether the review pushes the design toward implementation or whether it stays a design doc.
