Zakura proposes one-time keys for private ZEC swaps through NEAR Intents
The team behind Zakura says it wants each ZEC swap through NEAR Intents to use a separate key, limiting what a publicly visible refund address can reveal about a user's payment history.
By Chloe ·

The team behind Zakura is planning a privacy-focused change for ZEC swaps made through NEAR Intents. Under the proposal, every swap would receive its own key, designed to prevent a refund address recorded on NEAR’s public chain from exposing a user’s broader payment history.
Separating swaps from payment history
The issue centers on the information that can remain visible after a swap. A refund address is used to return funds if a transaction cannot be completed, but its presence on a public chain can create a link to other activity associated with that address.
Zakura’s proposed approach would avoid reusing the same key across swaps. Each transaction would instead be handled with a distinct key, making the refund information specific to that individual swap rather than directly connected to a wider record of payments.
Why the proposal matters
For users moving ZEC through an intent-based swap system, the change is aimed at preserving privacy across the full transaction process. The concern is not limited to the transfer of funds itself; it also includes the supporting addresses and refund arrangements that can be exposed while a swap is being processed.
The plan also reflects a broader concern around the long-term security of privacy-preserving cryptocurrency transactions. The original proposal is framed around keeping ZEC swaps private from future quantum computers, while the immediate design described by the team focuses on giving each swap its own key.
- Zakura wants each ZEC swap through NEAR Intents to use a separate key.
- A refund address remains visible on NEAR’s public chain.
- The proposed design is intended to reduce exposure of a user’s wider payment history.
- The plan is motivated by privacy concerns that include future quantum-computing threats.
The available details describe the intended design but do not provide a deployment date or technical timeline. For now, the proposal highlights how privacy can depend not only on the asset being transferred, but also on the way addresses and keys are managed around a swap.
Source: Coindesk

