What is KuraPrivacy?
KuraPrivacy is a privacy protocol that combines uncompromising on-chain transaction privacy with the operational robustness enterprises require. It enables applications such as wallets and payment services to achieve both privacy protection and regulatory compliance.
The problems KuraPrivacy solves
On public chains, token transfers — stablecoins among them — expose the sender, recipient, amount, token, and balance for anyone to observe. While this transparency is a defining feature of blockchains, it can conflict with the privacy that users and businesses expect in scenarios such as B2B settlement, in-store payments, and payroll.
At the same time, simply concealing transaction data raises the concern that it could become a conduit for money laundering and other illicit activity. This is a significant barrier for enterprises looking to adopt privacy-preserving solutions.
Furthermore, many privacy solutions require a dedicated signing key for operations on the privacy contract, separate from the user's ordinary wallet signing key. Users must manage multiple keys, which complicates the experience. For enterprises, the operational burden of issuing, storing, revoking, and handing over these additional keys adds further friction to adoption.
KuraPrivacy addresses these challenges on two fronts: strong privacy protection — anonymity, confidentiality, and unlinkability — together with regulatory compliance enabled by controls implemented at the protocol level.
Key features of KuraPrivacy
KuraPrivacy is not merely a mechanism for concealing transactions. It is designed to deliver privacy, operability, and the necessary controls simultaneously, in a form that existing wallets and payment services can readily adopt.
| Feature | Overview |
|---|---|
| Privacy-preserving transfers and value movement | KuraPrivacy lets you issue Kura addresses, deposit, transfer, withdraw, display balances, view history, and check execution status. All of this comes with anonymity (concealing who sent and received funds), confidentiality (concealing amounts and token types), and unlinkability (preventing the correlation of multiple transactions). |
| Selective disclosure | By default, strong privacy is maintained. When needed, you can share viewing keys with specific parties (such as regulators or service operators) so they can review the transaction history and balances of the relevant accounts. |
| Support for common signing methods | EOA, WebAuthn / passkey, multisig, and contract wallets can all operate on the same Kura address, policy, and recovery framework. Privacy features work seamlessly across all supported authentication methods, from consumer-facing passkey UX to multi-step organizational approvals. |
| Allowlist support | You can restrict transactions to pre-registered Kura addresses (accounts). This makes it easy to, for example, permit transactions exclusively from KYC-verified users. |
| Forced transfer and asset freeze | Based on predefined policies, assets held in the Kura Contract can be forcibly transferred without the standard transfer approval. Use cases include personnel departures, regulatory obligations, and emergency asset recovery. |
| Low-gas design | KuraPrivacy is highly gas-efficient, even among privacy solutions. Compared with Railgun (a leading alternative), which requires roughly 1,100,000 gas per deposit or transfer, Kura requires only about 400,000 gas — less than a third. |
| Multi-chain support | All EVM-compatible chains are supported at launch. Support for non-EVM environments such as Solana will be evaluated based on demand going forward. |
Key use cases
KuraPrivacy is well-suited to scenarios where privacy and regulatory compliance need to go hand in hand. Examples include:
- B2B transfers: Sending stablecoins without exposing counterparties or transaction amounts to competitors or unrelated third parties.
- Payroll: Processing salary payments on-chain without disclosing individual compensation amounts, particularly valuable for cross-border payments.
- In-store and service payments: Accepting stablecoin payments while keeping a merchant's sales history and revenue confidential, with audit support available when required.
- DAO / treasury operations: Managing inter-community transfers and treasury funds without publicly disclosing token holdings.
Why teams build with KuraPrivacy
- Privacy and regulatory compliance in a single architecture
- Many privacy solutions can conceal transaction data, but few can deliver meaningful compliance at the same time.
- By embedding controls such as selective disclosure, allowlists, and forced transfers directly into the protocol layer, KuraPrivacy delivers privacy protection and regulatory readiness together. It is designed to satisfy the governance requirements of enterprises and financial services without exposing user transaction data beyond what is strictly necessary.
- Integrate without rebuilding your existing auth or wallet stack
- Adopting KuraPrivacy does not require a significant overhaul of your existing user authentication or wallet experience.
- Signing methods already in use (passkeys, EOAs, multisig, contract wallets) connect directly to Kura. From simple consumer transfer flows to multi-step organizational approvals, everything runs on the same underlying foundation.
- ZK proofs, chain sync, and encrypted transaction management, abstracted at the service layer
- KuraPrivacy provides enterprises with an API-based service that handles the complex work: zero-knowledge proof generation, blockchain synchronization, and encrypted transaction state management.
- By integrating through the Service API, partners can add private transfer functionality to their products without touching ZK internals or on-chain state management directly. Development teams can stay focused on application experience and business logic rather than cryptographic infrastructure.
What to read next
- Integration Overview: Understand what is needed to integrate KuraPrivacy and explore the usage scenarios for each feature.
- Service API: A concise reference for the key endpoints of the HTTP API.