Hardware wallets will support Zakura's one-time viewing key design once their respective firmware accommodates the new key derivation process.

Overview Debates Related claims Topics Sources

Zakura developer Adam Tucker stated that a single published shielded address exposes payment histories until Project Tachyon's recursive proof upgrade deploys.

A quantum computer running Shor's algorithm could theoretically recover an incoming viewing key from a publicly exposed Zcash address to link an account's wider payment history.

Zcash developers have targeted January 2027 for introducing post-quantum signature opcodes to protect transparent transactions.

Zcash developer Zakura proposed assigning a one-time incoming viewing key to every ZEC swap routed through NEAR Intents to protect transaction privacy against future quantum computing risks.

NEAR Intents permanently publishes a user's Zcash refund address on NEAR's public blockchain during cross-chain swaps, creating a public record even if no refund occurs.

Zakura's design uses private information retrieval to enable wallets to look up refund transactions during restoration without exposing queried addresses to database operators.

Zakura rejected creating separate Zcash accounts for each transaction because Keystone hardware wallets sign only from account index 0 and Ledger devices require separate approvals for each account.

Zakura's proposal limits potential quantum exposure to a single swap while keeping a wallet's main spending key unchanged, maintaining funds under a single account.

Software wallets using Zakura's open-source libraries, such as Vizor, could integrate the per-swap viewing key feature within weeks.

Zcash Open Development Lab CEO Josh Swihart stated in May 2026 that between $600 million and $700 million had flowed through Zcash's NEAR Intents route.

Shielded Labs announced project Epoch on October 1, 2026, aiming to develop post-quantum cryptography for Zcash by the end of 2027.

Zakura already uses private information retrieval for Zcash coinholder voting lookups and transparent wallet monitoring.

Pirate Chain targets a maximum total supply ceiling of 200 million ARRR tokens

A source code flaw in the Pirate Chain privacy network allowed an unauthorized user to mint approximately 39.8 million ARRR tokens on October 14, 2026

The unauthorized minting of 39.8 million ARRR tokens represented roughly 20% of the total Pirate Chain token supply at the time of the October 14, 2026 exploit

The Pirate Chain development team proposed a blockchain rollback to revert the network to its state as of 20:00 UTC on October 14, 2026, discarding all subsequent blocks

Pirate Chain developers acknowledged that the cryptographically hidden nature of Sapling pool transactions complicates efforts to trace where the 39.8 million unauthorized ARRR tokens went

Pirate Chain enforces mandatory zk-SNARKs privacy shielding across 100% of its network transactions

Following the unauthorized minting of 39.8 million ARRR tokens on October 14, 2026, the illicit tokens were rapidly moved into Pirate Chain's Sapling shielded pool

The Pirate Chain network remained operational while developers worked on recovery, instructed wallet users not to move funds, and requested exchanges and mining pools voluntarily pause operations following the October 14, 2026 exploit that minted 39.8 million ARRR tokens