Zcash developers plan a fix to keep ZEC swaps private from future quantum computers
- Published
- Updated
- Since then
- 1 new report
Zakura proposed a Zcash privacy update for swaps made through NEAR Intents, giving each ZEC swap its own viewing key so one public refund address would reveal less of a user’s wider history. The design is still under review and has not been shipped.
Key claims & sources
What it means
Zcash's shielded pool has long relied on viewing keys to let a user selectively disclose transaction details without exposing their full history, a design that predates NEAR Intents, the cross-chain swap protocol that lets ZEC move against assets on other chains by posting a refund address on NEAR's public, non-shielded ledger. That refund address is the weak point: because NEAR's chain is transparent, a single exposed address can in theory be used to work backward into a user's broader shielded payment history if the cryptography protecting it is ever broken. Zakura, the team building Zcash node and wallet infrastructure, frames this as a problem worth solving before it becomes urgent rather than after.
If adopted, wallet software built on Zakura's work would generate a distinct viewing key for every swap routed through NEAR Intents, rather than reusing one key across a user's transactions. Wallet developers integrating with NEAR Intents would need to rebuild key-management logic to issue and track these per-swap keys, and users would see no change in how a swap feels but would gain protection against any single leaked address being used to link their other swaps together. The ones who lose nothing and gain the most are frequent swappers, whose repeated use of NEAR Intents is exactly the pattern that would otherwise build up a traceable history; wallets that skip the upgrade would leave that pattern exposed.
The proposal sits inside a broader and still unsettled argument in cryptocurrency engineering about how seriously to treat quantum computing as a near-term threat versus a distant one, an argument that has also surfaced around Bitcoin address reuse and key exposure. Hardening a privacy coin's cross-chain swap mechanism against a computer that does not yet exist is a defensible bet given how slow wallet upgrades are to roll out once a threat is confirmed, but it is also a resource commitment that competes with features users want today. Zcash's bet is that shielded-pool privacy is the product's core promise, so a design flaw that only matters in a future scenario is still worth closing now rather than waiting for proof the risk is real.
Zakura's engineering page currently lists the per-swap viewing key design as in review, with no shipping date attached and no confirmation yet that wallet providers integrating with NEAR Intents will adopt it. The decision to watch is whether the design clears review and gets built into production wallet software, since a proposal that stays on an engineering roadmap offers no protection to anyone actually swapping ZEC through NEAR Intents today. Adoption by multiple wallets, not just a published design, is what would turn this from a documented fix into a shipped one.
Market reaction i
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Unchained
context