Zama's Genesis Operators:The Heroes Behind The Future of FHE in Web3 Privacy
I’m very passionate about AI and DeFi privacy which is why I have been excited about what @zama_fhe just unveiled: the 4th Genesis Operator @P2P validator. They have been around since 2018 and provide Web3 security validating for Ethereum and Cosmos and many others and currently protecting Zama’s private FHE key using Multi Party Computation (MPC).To me, this is not just an announcement and I’m sure many in the node operator community see it as a clear example of decentralized trust in action.
I’ll quickly explain: Zama Protocol starts with 18 operators (13 KMS nodes for key generation/threshold decryption + 5 FHE Coprocessors for encrypted compute). Early picks like @Figment_io, securing over $17B in assets, @conduitxyz which is powering appchains and on chain games, and @InfStones which protects over $5B, are doxxed pros with skin in the game - equity ties and revenue shares, which I also think is a cool way to ensure they are fully committed. Zama is securing many $B assets through the players and operators in the ecosystem and Zama Protocol.
Why this is important to privacy devs:Those operators in the fhEVM context are the DPoS layer in the system.There is no single place of failure, the system is composable, and censorship resistant.Think private DeFi swaps where bids are only revealed after a final decision is https://t.co/InVr27p8SJ also includes AI models that are trained without decryption on sensitive and private health data.Stash MPC is also used to avoid single points of failure with the FHE key split across nodes. Audit is by Trail of Bits.
From Zama’s litepaper:Operators receive $ZAMA rewards. They also stake 0.5% of the circulating supply to join later. This addition of the economic layer plus reputation gating equals bulletproof security. As the testnet v0.10 has reached 1000+ TPS with GPU boosts, these operators are making confidential blockchains scalable.
I nailed it: FHE > ZK for runtime privacy. Who’s building with fhEVM? Drop your use cases below.
let’s secure the future together!
#ZamaCreatorProgram
Zama's Genesis Operators:The Heroes Behind The Future of FHE in Web3 Privacy
I’m very passionate about AI and DeFi privacy which is why I have been excited about what @zama_fhe just unveiled: the 4th Genesis Operator @P2P validator. They have been around since 2018 and provide Web3 security validating for Ethereum and Cosmos and many others and currently protecting Zama’s private FHE key using Multi Party Computation (MPC).To me, this is not just an announcement and I’m sure many in the node operator community see it as a clear example of decentralized trust in action.
I’ll quickly explain: Zama Protocol starts with 18 operators (13 KMS nodes for key generation/threshold decryption + 5 FHE Coprocessors for encrypted compute). Early picks like @Figment_io, securing over $17B in assets, @conduitxyz which is powering appchains and on chain games, and @InfStones which protects over $5B, are doxxed pros with skin in the game - equity ties and revenue shares, which I also think is a cool way to ensure they are fully committed. Zama is securing many $B assets through the players and operators in the ecosystem and Zama Protocol.
Why this is important to privacy devs:Those operators in the fhEVM context are the DPoS layer in the system.There is no single place of failure, the system is composable, and censorship resistant.Think private DeFi swaps where bids are only revealed after a final decision is https://t.co/InVr27p8SJ also includes AI models that are trained without decryption on sensitive and private health data.Stash MPC is also used to avoid single points of failure with the FHE key split across nodes. Audit is by Trail of Bits.
From Zama’s litepaper:Operators receive $ZAMA rewards. They also stake 0.5% of the circulating supply to join later. This addition of the economic layer plus reputation gating equals bulletproof security. As the testnet v0.10 has reached 1000+ TPS with GPU boosts, these operators are making confidential blockchains scalable.
I nailed it: FHE > ZK for runtime privacy. Who’s building with fhEVM? Drop your use cases below.
let’s secure the future together!
#ZamaCreatorProgram