The privacy-focused cryptocurrency Zcash is confronting a long-term threat that has little to do with today’s transaction speeds or wallet interfaces. A development team working on Zakura has proposed a change to how ZEC swaps are handled through NEAR Intents, an intent-based cross-chain system that can leave refund addresses on a public ledger. The proposal would assign a separate viewing key to every swap, limiting what a future quantum computer could learn if it eventually gained the ability to analyze public blockchain data at scale. The aim is not to redesign Zcash from the ground up, but to close a specific leak that could become more dangerous as quantum research advances.

Zcash has long offered shielded transactions that hide sender, receiver, and amount using zero-knowledge proofs. To make selective disclosure possible, the network supports viewing keys: cryptographic material that lets a holder see transaction details without gaining the ability to spend funds. Spending keys remain the ultimate control mechanism. That separation is central to the new proposal. If a refund address is posted publicly, the concern is that it could be used as a starting point for linking swap activity to a broader payment history. A per-swap viewing key would keep that disclosure narrow, so a single refund event does not become a master key for a user’s entire financial trail.

NEAR Intents is designed around a simple idea: a user states what they want to trade, and competing solvers execute the trade. The model can improve pricing and reduce friction across chains, but it also creates operational touchpoints. If a swap fails, the user may need a refund address to recover funds. That address can be visible on NEAR’s public chain. Over time, analysts can cluster addresses, trace repeated interactions, and infer relationships. In a world with powerful quantum computers, data that looks harmless today could be re-examined later. Zakura’s proposal addresses that harvest-now, analyze-later risk by making each swap’s disclosure scope independent.

Key facts at a glance

• Zakura wants a separate viewing key for every ZEC swap made through NEAR Intents.
• The change is meant to limit the payment history that a future quantum computer could uncover from a publicly posted refund address.
• Spending keys would stay with users.
• Private information retrieval would help wallets locate refunds without revealing which addresses they are checking.
• Compatible wallets could adopt the open-source feature within weeks.
• The work is timed ahead of a January target for quantum-resistant payments from Zcash developers.

Private information retrieval, or PIR, is the second part of the design. In a normal refund lookup, a wallet might ask a server whether a particular address has a pending refund. That query can reveal the address being checked, even if the transaction itself is private. PIR allows a wallet to retrieve information from a database without telling the server which item it requested. In this context, it could let a wallet check refund status while hiding the set of addresses under consideration. The combination matters: per-swap viewing keys limit what can be disclosed, while PIR limits what is leaked during the lookup process. Together, they aim to prevent the refund workflow from becoming a surveillance channel.

Keeping spending keys with users is a deliberate design choice. The proposal does not turn Zakura, NEAR Intents, or any solver into a custodian. A viewing key can reveal transaction details for a defined purpose, but it cannot move funds. That distinction is important for users who want privacy without surrendering control. It also gives wallet developers a clear boundary: they can implement refund discovery and disclosure features without holding the keys that authorize spending. If the feature is open source, compatible wallets could integrate it without waiting for a centralized rollout, which may explain why the team believes adoption could happen within weeks rather than months.

The quantum threat to public-key cryptography is still prospective, but it is serious enough that governments, standards bodies, and blockchain developers are preparing for it. A sufficiently powerful quantum computer running Shor’s algorithm could break elliptic-curve cryptography, which underpins many digital signatures and key exchanges. Zcash, like many cryptocurrencies, relies on elliptic-curve constructions in parts of its protocol. Quantum computers could also weaken symmetric cryptography, though the impact depends on key sizes and algorithms. The more immediate concern is data collection: an adversary can record public blockchain data today and wait for future decryption or analysis capabilities. Privacy systems that depend on long-term secrecy must therefore consider not only current attackers but also future ones.

Zcash developers have set a January target for quantum-resistant payments, according to the proposal’s context. That target suggests the ecosystem is already moving toward post-quantum signature schemes and related upgrades. Zakura’s fix is narrower. It does not make every Zcash transaction quantum-proof, and it does not replace the need for protocol-level changes. Instead, it tries to reduce the privacy damage that could occur at the edges of the system, where swaps, refunds, and wallet queries meet public chains. In that sense, the proposal is a complement to broader quantum-resistance work rather than a substitute for it.

Wallet adoption will determine whether the proposal has practical effect. A privacy feature that exists only in a specification does not protect users. The team says compatible software wallets could adopt the open-source feature within weeks. That timeline is plausible if the change can be implemented as a wallet-level upgrade rather than a consensus change. Wallets would need to generate per-swap viewing keys, manage refund discovery through PIR, and present disclosure controls in a way users can understand. The hard part may be user experience: privacy features often fail when they add friction. A design that hides complexity while preserving user control has a better chance of being used by default.

Several challenges remain. PIR systems can be computationally expensive, and performance may vary depending on the database size and query pattern. Wallets must also guard against metadata leaks outside the refund lookup itself, including timing, IP addresses, and repeated query behavior. Per-swap viewing keys add key management overhead. If users lose a viewing key, they may lose the ability to audit a refund; if they share it too broadly, the privacy benefit shrinks. The proposal’s success will depend on clear defaults, robust recovery options, and audits. It will also depend on solvers and infrastructure providers respecting the separation between viewing and spending authority.

The broader significance is that privacy is becoming a cross-chain problem. A shielded transaction can be private on one network, but a swap or refund on another network can create a public footprint. Attackers do not need to break Zcash’s cryptography if they can correlate addresses, timing, and refund behavior across chains. That is why per-swap keys and private refund lookups matter. They treat the public chain as a place where metadata can accumulate, and they try to prevent a single operational address from becoming a permanent identifier. As cross-chain swaps grow, these edge cases will matter more, not less.

Privacy advocates are likely to welcome the proposal because it strengthens selective disclosure without weakening spending security. Regulators and compliance teams may also see value in a design that allows refunds to be audited when necessary while limiting unnecessary exposure. The key question is whether the feature can be standardized across wallets and swap providers. If it remains optional and inconsistently implemented, users may still fall back to reusable refund addresses. If it becomes a default in compatible wallets, it could raise the baseline privacy of ZEC swaps without requiring users to understand viewing keys or PIR.

The proposal arrives as Zcash developers pursue a January target for quantum-resistant payments, but the two efforts operate on different layers. The January work addresses the cryptographic foundations of payments. The Zakura proposal addresses how privacy is preserved when ZEC moves through NEAR Intents and refunds are posted publicly. For users, the practical result could be a swap flow that keeps spending keys local, reveals only what a specific refund requires, and avoids turning a public refund address into a map of past transactions.

Source: Coindesk News