Zakura Develops One-Time Viewing Key Fix for Quantum Zcash Swap Risks

Zakura published an engineering proposal on Oct. 19, 2026, detailing a defense against future quantum decryption attacks targeting $ZEC cross-chain swaps ¹. The vulnerability affects users who publish shielded addresses to public ledgers during automated swap processes, particularly through protocols like NEAR Intents ¹.

Under Zcash's current cryptographic design, shielded transactions hide recipient and public-key data from classical and quantum observers on the native ledger ¹. However, when an address is permanently published to an external public blockchain—such as a refund destination recorded on NEAR's public network—an adversary with a sufficiently advanced quantum computer running Shor's algorithm could derive the user's incoming viewing key ($ivk$) ¹. Because standard Zcash accounts rely on a single $ivk$ across all diversified addresses, compromising that key would expose the value, memo, and linkability of every transaction the account has ever received ¹.

Isolating Addresses Without Account Fragmentation

To eliminate the risk of chain-wide de-anonymization prior to the launch of Zcash's Tachyon upgrade, Zakura designed a "one-time $ivk$" architecture that wallets can adopt directly ¹. Standard naive workarounds involve generating a new account for each swap, but hardware wallet limitations make that approach unwieldy ¹. For instance, Keystone hardware signers only access account index 0, while Ledger devices require separate transactional approvals for every account index ¹.

Zakura's method instead modifies key derivation by producing a unique randomized secret ($rivk$) per swap index via keyed hashing, while leaving spending keys ($ask$) and nullifier derivation keys ($nk$) untouched ¹. This ensures that all incoming funds remain spendable from a single unified balance without manual multi-account approvals ¹. If a quantum computer subsequently cracks an exposed swap address, the attacker recovers only the isolated viewing key for that specific transaction ¹.

To resolve wallet-recovery scanning overhead created by multiple viewing keys, Zakura implemented private information retrieval (PIR), adapting lookup mechanisms previously deployed for Zcash coinholder voting ¹. The update arrives as infrastructure operators expand zero-knowledge integrations, following steps such as when Gemini migrated Zcash infrastructure to Zakura node capabilities ¹. Zakura indicated that client software can integrate the derivation pattern immediately ahead of long-term post-quantum upgrades ¹.