Zama's Threshold Key Management System
Multiparty FHE requires a shared decryption between parties. However, managing and securing private keys across multiple parties is challenging and increases the risk of unauthorized access.
It Enables Secure and Robust FHE Key Generation and Decryption*
*A Key Management Service (KMS) is used to secure cryptographic keys.
Fully Decentralized Private Key
Private keys are distributed in the decentralized network, enhancing security.
Resistant to DoS Attacks
Only 2/3 of the KMS nodes are required to maintain the service.
Verifiable and Auditable
Prevent bribery and blackmailing by ensuring votes remain private and protected throughout the process.
Enterprise-Grade Security*
Via a Defense-In-Depth Approach
*Security audit and certification is ongoing, and will be completed soon.
PoA Blockchain
The integrity and verifiability of decryption requests are ensured via a Proof of Authority blockchain consensus.
Threshold MPC
Security and liveness is guaranteed via a robust threshold MPC protocol for key generation and decryptions.
Secure Enclaves
Offchain collusion is prevented by keeping the private key shares inside a secure enclave such as Amazon Nitro.
Legal Contracts
Nodes are chosen based on reputation and experience, and sign a legally binding agreement to behave honestly.
Zama's TKMS Enables Secure
and Robust FHE Key Generation and Decryption
Using Zama's TKMS is as easy as 1, 2, 3
1. Configure the KMS
It can be configured via Zama's developer console, or by uploading a configuration smart contract to the KMS chain.
2. Generate Your FHE Keys
Threshold key generation is triggered via Zama's developer console, or by submitting a transaction to the KMS chain.
3. Decrypt Ciphertexts
Decrypting FHE ciphertexts is done via an API call, or by submitting a transaction directly to the KMS chain.
ALREADY POWERED BY ZAMA
Join The Zama Developer Newsletter
Receive only what matters to you, like product releases, tutorials, bounties, and other great opportunities.
No spam, never.