Zcash Developer Zakura Proposes Per-Swap Keys to Protect ZEC Privacy
Zcash developer Zakura is proposing that each ZEC swap through NEAR Intents use its own key. The change is intended to stop a refund address visible on NEAR's public blockchain from connecting a user's swaps to their broader Zcash payment history.
Key takeaways
- Zakura proposes giving each ZEC swap through NEAR Intents its own key.
- NEAR's public blockchain can expose a refund address associated with a swap.
- Zakura warns that one published Zcash address could let a future quantum attacker link every payment a wallet has received.
- The proposal has no reported deployment date.
Zcash developer Zakura is proposing a privacy fix for ZEC swaps made through NEAR Intents: give each swap its own key. The goal is to prevent a refund address published on NEAR's public blockchain from revealing the wider payment history associated with a user's Zcash wallet.
Zakura warns that publishing a single Zcash address could let a future quantum attacker link every payment a wallet has ever received. The proposal aims to limit what can be connected if information about a particular swap becomes public; it is a planned change, not a report that quantum computers can currently break Zcash privacy.
How would separate keys protect ZEC swaps?
NEAR Intents lets users swap assets across blockchains, but a refund address can be exposed on NEAR's public chain. If the same Zcash address is reused, that public link could provide a starting point for tracing other activity associated with it.
Under Zakura's proposal, each swap would use a distinct key instead of relying on one address across transactions. That would make a public refund detail less useful for connecting separate swaps or exposing a wallet's broader payment history. It is a targeted privacy measure, not a claim that every part of a cross-chain swap becomes private.
What should ZEC users watch for?
The report describes a proposed fix, not a deployed feature, and does not provide a rollout date. Users should look for confirmation from Zakura or NEAR Intents about implementation and whether it changes how refunds are handled.
The issue is specific to the boundary between Zcash's shielded payments and NEAR's public transaction records: privacy on one chain can be weakened by information exposed on another. That distinction matters for anyone using cross-chain swaps, where the public side of a transaction may reveal more than the private asset's own network does. It also differs from broader quantum-readiness work, such as Ethereum's proposed post-quantum signature changes, which focus on the security of network signatures rather than address reuse in a swap flow.
Frequently asked questions
What is Zakura proposing for Zcash swaps?
Zakura wants each ZEC swap through NEAR Intents to use its own key, so a public refund address is less able to link transactions to a user's broader Zcash payment history.
Can quantum computers currently trace Zcash payments?
The report discusses a risk from future quantum computers. It does not say that quantum computers can currently break Zcash privacy.
Is the per-swap key fix already live?
The report describes a proposed fix and gives no rollout date or confirmation that it has been deployed.