TL;DR: Zakura has proposed assigning a separate viewing key to each Zcash swap made through NEAR Intents, reducing how much transaction history a future attacker might be able to link.
Zcash’s privacy model is built around shielding transaction details, but cross-chain swaps introduce awkward points where information can become public. A new proposal from Zcash software developer Zakura focuses on one of those points: the refund addresses involved when shielded ZEC moves through NEAR Intents.
A publicly visible address can be linked to a wallet’s viewing-key structure. If future cryptographic advances allowed an attacker to recover or exploit that relationship, exposing one address could reveal more of a user’s transaction history than intended.
Zakura’s proposed answer is to give each swap its own viewing key while leaving spending authority under the user’s control. A compromised viewing key would then reveal information related to one swap, rather than opening a window onto an entire wallet’s past.
The design also contemplates private information retrieval, allowing software to locate relevant refunds without broadcasting which addresses a user is checking.
This isn’t a response to a demonstrated quantum attack against Zcash. It is preventative engineering based on a possible future risk. The proposal remains under review, and supporters have not yet delivered a widely deployed solution.
That distinction matters. Good privacy work often means fixing linkability problems before they become exploitable, but protection must still be implemented, audited and adopted by wallets before it benefits ordinary users.
Written by the News Desk and edited by Samuel Rae.
[#content_wordai]
