The Zama Confidential Blockchain Protocol enables confidential smart contracts on top of any L1 or L2 using FHE.
Blockchain transparency is a bug, not a feature
Why? Because validators need to see the data to verify the state
But confidentiality and public verifiability is possible
Powered by Fully Homomorphic Encryption (FHE).
Zama uses FHE to keep onchain data encrypted at all times, even during processing. Not familiar with FHE? Learn more about it here.
Scalable, secure and affordable.
Zama uses coprocessors to offload the FHE computation from the base chain. This keeps gas fees low while enabling horizontal scalability and public verifiability.
Opening a myriad of new use cases for DeFi
DeFi
Confidential token swaps, lending, and yield farming.
Payments
Confidential stablecoin transactions with encrypted amounts
Banking
Onchain self-custodial banking with full confidentiality.
Tokens
Confidential token launches, vesting, airdrops, and governance.
RWA Tokenization
Confidential and compliant RWA to boost institutional adoption.
Sealed-bid auctions
Confidential and fair onchain auctions preventing front-running.
contract EncryptedERC20{
// ...
function transfer(address to, einput encryptedAmount, bytes calldata inputProof) public {
ebool canTransfer = TFHE.le(amount, _balances[msg.sender]); // Ensure owner has enough tokens
euint64 transferValue = TFHE.select(isTransferable, amount, TFHE.asEuint64(0));
euint64 newBalanceTo = TFHE.add(_balances[to], transferValue); // Add to the balance of `to`
_balances[to] = newBalanceTo;
TFHE.allowThis(newBalanceTo);
TFHE.allow(newBalanceTo, to);
euint64 newBalanceFrom = TFHE.sub(_balances[from], transferValue); // Subtract to the balance of `for`
_balances[from] = newBalanceFrom;
TFHE.allowThis(newBalanceFrom);
TFHE.allow(newBalanceFrom, from);
}
}
Solidity is all you need.
Zama contracts are simple solidity contracts that are built using traditional Solidity toolchains.
Simple developer experience.
Developers can use the euint data types to mark which part of their contracts should be private.
Programmable compliance.
Define all the rules for who can decrypt what directly in your smart contract, according to your own compliance needs.
Making FHE practical for most use cases
Zama is already faster than Ethereum
Zama can already process 20 tps / chain, enough to run all of Ethereum with FHE, and will reach 1,000 tps next year.
FHE ASICs will enable 10,000+ tps
We're partnering with multiple hardware companies to create dedicated ASICs for FHE, which will enable thousands of tps.
FHE is the holygrail of cryptography
Zama Protocol Roadmap
Zama Newsletter
No spam, ever.