Confidential Stablecoin using Fully Homomorphic Encryption
Add compliant confidentiality to your stablecoins projects leveraging Fully Homomorphic Encryption (FHE).
Read white paper
Read white paper
Read white paper
Read white paper
Read white paper
Read white paper
Lack of confidentiality of stablecoins affects their effectiveness, regulatory compliance and overall credibility.
Unlock a Myriad of New Use Cases With Confidential Stablecoins
Using the power of Fully Homomorphic Encryption (FHE).
Confidential RWA
Tokenization
Confidential security tokens cannot be fully onchain if the stablecoin used to buy or liquidate the token or to pay dividends or interest is not itself confidential.
Remittance
Transfers
Many destination countries of remittance transfers are countries with high crime rates. A clear remittance amount on a public blockchain puts the receiving party at risk.
Corporate
Payments
Competitors can gather valuable intelligence on a company if all of its payments are publicly available in clear.
Charity
Donations
Use confidential stablecoins to make anonymous donations, protecting the privacy of donors and ensuring secure contributions.
Salaries
and Compensations
Most employees would object to have their compensation details public. It is also illegal to do so in some countries.
Withholding
Taxes
In some countries, withholding tax rates on incomes reveal personal information about the receiver such as overall income bracket and family situation.
Use a Turnkey FHE Solution to Make Your Stablecoin Confidential
FHE Coprocessor
Encryption of balances and transactions
All balances and transaction values are encrypted.
Blind stablecoin transfers
Executes all stablecoin transfers blindly without knowing the transaction values and the resulting balances.
Compliance conditions in transfers
Transfer smart contract can include compliance conditions such as blacklists and nationalities if needed.
All balances and transaction values are encrypted.
Blind stablecoin transfers
Executes all stablecoin transfers blindly without knowing the transaction values and the resulting balances.
Compliance conditions in transfers
Transfer smart contract can include compliance conditions such as blacklists and nationalities if needed.
+
Threshold Key Management System
Default decryption
By default, the KMS only allows the sender and the receiver to decrypt the transaction values.
Optional decryption
Through explicit coding in the transfer smart contract, other parties such as the money transfer agent providing the transferred cash to end users, the wallet network, regulators and law enforcement relevant to senders and receivers can be enabled to decrypt.
By default, the KMS only allows the sender and the receiver to decrypt the transaction values.
Optional decryption
Through explicit coding in the transfer smart contract, other parties such as the money transfer agent providing the transferred cash to end users, the wallet network, regulators and law enforcement relevant to senders and receivers can be enabled to decrypt.
Ready to implement FHE?
Take a deep dive into our tech or contact our team to get started.
Are you a developer?
Discover our open-source libraries on Github and explore our developer resources to implement FHE with Zama.
See on Github
Talk to the Zama team
Leverage FHE using Zama’s libraries, products, and solutions to unlock new privacy-enhancing capabilities.
Start conversation