Zcash developers are targeting January for tools that could protect transparent ZEC payments against future key-recovery attacks without making wallet activity easier to trace today.
Key Takeaways
- Zcash developers are targeting January for post-quantum signature tools.
- The work focuses on transparent addresses and public payments.
- Fresh addresses can reduce repeated public-key exposure.
- Private wallet lookups aim to prevent address linking.
January’s target focuses on transparent ZEC
Zakura, the team developing Zcash infrastructure, says it plans for post-quantum signature opcodes to land in January. The proposal centres on transparent payments, where addresses, amounts and transaction history remain visible on the blockchain and where most circulating ZEC is currently held.
A new engineering post describes a wallet design that combines those signatures with rotating transparent addresses and private information retrieval, known as PIR. The components tackle a future cryptographic risk while addressing a privacy weakness that would otherwise appear when wallets begin using many fresh addresses.
Transparent Zcash addresses initially contain a hash of a public key. The public key itself becomes visible when the address spends, allowing the network to verify the payment signature. If future technology made it possible to recover a private key from that public key, any funds left at the same address, or sent there later, could face greater exposure.
Fresh addresses keep later funds behind a new key
Address rotation gives a wallet a way to reduce that repeated exposure. After an address spends, the wallet can move its remaining balance to a newly derived address. That new address is tied to a different public key, whose hash remains visible while the key itself remains undisclosed.
The approach does not require someone to open a new wallet or record another recovery phrase after every payment. A standard wallet seed can derive a sequence of separate addresses and key pairs, allowing the software to create new receiving and change addresses from one existing backup.
That separation also depends on protecting the wallet’s extended public-key and viewing information. Those records can reveal more about a wallet’s address structure than an ordinary transaction, weakening the benefit of keeping each public key separate.
Wallet lookups can reveal the links that the blockchain does not
Generating new addresses creates a practical problem: the wallet still needs to find incoming payments, track funds it has spent and rebuild history after a recovery. A normal light wallet may ask a server for activity associated with address A, then B, then C.
Those addresses can appear unrelated on the blockchain, but the server sees the requests arriving from the same wallet. It can therefore connect the addresses even when the public ledger alone does not provide that link.
Zakura proposes PIR to avoid that leak. The wallet retrieves the record it needs from a server without revealing which record it selected. It can also download compact public activity filters, check them locally for possible matches, and make a private request only when a block range may contain relevant history.
Transparent payment data would remain public on the Zcash blockchain. PIR narrows the extra information exposed when a wallet asks a service to monitor several addresses, preserving the purpose of rotating them in the first place.
The proposal addresses a long-term risk, not a current emergency
The design speaks to the same concern raised in Europol’s warning about exposed wallet keys. A sufficiently capable future attacker could target a public key that has appeared on-chain, making older address-reuse habits less safe than they are today.
Neither Europol nor Zakura says that a practical quantum attack is currently available. The challenge is preparing wallet software, infrastructure providers and users before a cryptographic migration becomes urgent.
What remains visible and unchanged
- Transparent transaction details remain public on-chain.
- Privacy still depends on wallet behaviour and the services a user connects to.
- The announcement introduces no ZEC swap, wallet migration or new recovery phrase.
Private queries arrive before the signature goal
Zakura says the PIR component is reaching its Vizor wallet first. Users can test the experimental feature by enabling “Private queries” in the wallet settings, giving the team a way to evaluate how private history retrieval works before the wider signature changes arrive.
The January milestone concerns the post-quantum signature opcodes for transparent pools. Wallets and services will still need to support the updated payment flow, so the date is a development target rather than a guarantee that every transparent Zcash wallet will receive the protection at once.
Zcash is preparing the wallet layer early
The usefulness of the plan lies in pairing stronger payment authorization with the wallet infrastructure needed to use it privately. Fresh addresses can reduce future public-key exposure, while PIR can keep the resulting address set from becoming a readable map of one user’s funds.
That is the practical goal behind Zcash’s January work: prepare transparent wallets for a future cryptographic threat without creating a new privacy problem in the process.
This article is for informational purposes only and does not constitute investment, security or technical advice. The January timing is a development target and may change as the work progresses.
Be the first to comment