Zcash Developer Proposes One-Time Keys to Stop Quantum Linking of NEAR Swaps

A Zcash full node developer has proposed one-time viewing keys to prevent future quantum computers from linking shielded payments, especially swaps posted on NEAR’s public chain. This matters for privacy-focused crypto communities and wallet operators.

What happened

Zcash full node developer Zakura has proposed a privacy fix aimed at a future threat: a single published Zcash address could let a future quantum attacker link every payment a wallet has ever received. The proposal, introduced in an engineering post by Zakura developer Adam Tucker announced on Sunday, centers on "one-time" viewing keys designed to stop that linking.

The method targets swaps made through NEAR Intents, where a user's shielded address is posted on NEAR's public chain. Zakura said the approach needs no network upgrade, calling it "post-quantum unlinkable swaps for Zcash." Zcash's shielded transactions already hide the sender, recipient and amount, but each shielded account has a single incoming viewing key behind all of its addresses, which creates the linking risk the fix addresses.

Key facts

• Zakura, a developer of Zcash full node software, proposed the fix; the engineering post was by Zakura developer Adam Tucker and announced on Sunday.
• The fix targets swaps through NEAR Intents because the user's shielded address is posted on NEAR's public chain.
• Zakura called the approach "post-quantum unlinkable swaps for Zcash" and said it needs no network upgrade.
• Wallets built on Zakura's open-source libraries, such as Vizor, will be able to add the feature in the coming weeks, with hardware wallets to follow.
• Zcash shielded transactions hide sender, recipient and amount; each shielded account has a single incoming viewing key behind all of its addresses.

Our analysis

This matters because privacy features can be undermined by auxiliary data. The source describes the risk directly: a single published Zcash address could let a future quantum attacker link every payment a wallet has ever received. That is likely to concern privacy-focused users, especially those who interact with cross-chain systems such as NEAR Intents where shielded addresses become public artifacts.

The proposal is notable because it does not require a network upgrade. That lowers coordination cost and suggests wallets can adopt it independently. If the fix works at the wallet layer, it may reduce the need for urgent consensus changes, but it also concentrates initial adoption in tools built on Zakura's libraries. The timing mention—coming weeks for Vizor, hardware wallets to follow—suggests a phased rollout rather than immediate ecosystem-wide coverage.

For crypto communities, the key difference from prior privacy discussions is the specific bridge between shielded Zcash payments and NEAR's public chain. Operators should treat this as a protocol-adjacent development, not a market event. The likely short-term effect is educational: users need to understand why one-time viewing keys matter before they trust them.

What it means for operators

• Track Zakura and Vizor release notes if your community touches Zcash or NEAR Intents; the source says Vizor support is expected in the coming weeks, so prepare user-facing explainers for when wallets add the feature.
• Update privacy guides and support answers to distinguish shielded transactions from the new one-time viewing key behavior; avoid implying this is an investment development or price signal.
• Monitor whether hardware wallet support follows as described, and clarify which wallets need manual action versus automatic updates.
• Educate moderators and community managers on the specific risk: a single published shielded address on NEAR's public chain could allow future quantum linking, so community members should not treat public address sharing as harmless without context.

This article is news and operational analysis only, not investment advice.