Latest news: @ zama_he announces that the second creation operator is @ coinuitxyz. Those familiar with Conduit know that it is the type of service provider that provides a "bottom-up infrastructure" for teams, from Appchain to blockchain games and DEX. This entry is not a nominal platform, but to join Zama's decentralized MPC computing node cluster, which, like the previously announced @ Figment_io, is responsible for guarding the shards of FHE private keys. The key is split into shares and distributed among 18 operators (KMS and FHE co processors in parallel), and no one can obtain the full key. Confidentiality and verifiability are simultaneously preserved, which is the underlying paradigm of "verifiable privacy". With the recently launched FHEVM v0.9, developers can basically use it as an "encrypted version of EVM": Solidity writes confidentiality contracts in place; Generate/manage FHE keys on the chain; On demand scheduling of the coprocessor network, throwing recalculations to the acceleration layer; The entire execution path is end-to-end encrypted, and balance, price, and counterparties are not exposed. Imagine placing an order on DEX, where only the 'result is correct' is publicly available on the chain, and the process is a black box for any observer. This is not sacrificing transparency, but preserving verifiability without exposing data. Many people ask about performance and cost. Official public testing shows that Zama has achieved the level of "thousand TPS, one ten thousandth of a dollar" for confidential computing, and has provided an acceleration route from GPU to FPGA to ASIC, with the goal of doubling the number of grades. More importantly, it is not building a new chain from scratch, but rather as a privacy execution layer stacked on top of the existing L1/L2, with EVM taking the lead and SVM already planned on the route; For developers, the difference lies in not migrating assets, not changing languages, and not losing composability. Looking at it in a larger technological spectrum: TEE relies on specific hardware and licensing environments, and the anti attack boundary is determined by the vendor; ZK is strong in hiding data, but maintaining a complete and composable global state for DeFi requires high thresholds and reconstruction costs; FHE takes the path of "computing directly on ciphertext", which preserves the composability of public chains while achieving predictable acceleration with the advancement of general hardware. This is also why I am optimistic about Zama: it elevates privacy from a "patch" to a "default layer". On the community side, @ zama_he Creator Plan's third season is coming to an end, and the ecosystem tools from Concrete/Concrete ML to FHEVM have been put in place; On the protocol side, the list of operators is still being revealed. My judgment is simple: whoever first implements "confidential contracts+decentralized MPC+composable execution" will hold the discourse power of the next round of Web3 infrastructure. Zama is gradually implementing this matter, and the addition of Conduit is one of the key puzzles. ZamaCreatorProgram