Just saw that the official team has started announcing the genesis operators for the @zama_fhe protocol. The privacy layer has truly entered the 'operational' phase this time. The network adopts Delegated Proof of Stake, with an initial batch of 18 operators going live: 13 of them are responsible for KMS (Key Management), and 5 handle FHE co-processing power. More operators will be added gradually in the future, expanding the ceiling for security and throughput. Zama's key-side design is quite sophisticated: private FHE keys are split into multiple shares and safeguarded by a decentralized MPC network, with no single operator holding more than one share. This ensures confidentiality while retaining on-chain verifiability, breaking down the old dilemma of 'privacy vs. transparency' into a solvable engineering problem. The first publicly announced genesis operator is Figment. As a leading independent staking infrastructure provider, Figment offers nodes and custodial services to thousands of institutions, managing assets in the tens of billions of dollars. Having such a team handle the critical KMS/co-processing aspects is a perfect match for Zama's privacy contract approach. For developers, @zama_fhe's FHEVM v0.9 is also a milestone version: on-chain generation and management of FHE keys, an on-demand co-processor network, and the execution path for 'end-to-end encrypted computation' are all in place. You can continue writing contracts in Solidity, but inputs, states, and intermediate results remain encrypted—imagine completing a Swap on a DEX, where observers can only see the correct settlement but have no visibility into your price or quantity. Over the next few days, the official team will keep announcing more genesis operators. Teams interested in building confidential DeFi, privacy governance, or encrypted auctions can start setting up their environment now and use v0.9 to run their first prototype. ZamaCreatorProgram