Enclave is beyond the research and proof-of-concept stage. ZK + MPC + FHE. It's real, and it's happening.

@hashcloak @NoirLang @0xPolygonMiden @dWalletLabs @TACEO_IO @FireblocksHQ @cursive_team @PrivacyScaling @taikoxyz @SecretNetwork @zama_fhe @SunscreenTech @inconetwork @FHEOnchain @Ingo_zk Hence, if we are thinking about a privacy stack that will be expressive enough that developers can build any Web3 dApps they imagine, from everything we’ve mentioned in the article, we either have MPC-ZK (MPC is utilized for shared state) or ZK-MPC-FHE.

As for today, client-side

@hashcloak @NoirLang @0xPolygonMiden @dWalletLabs @TACEO_IO @FireblocksHQ @cursive_team @PrivacyScaling @taikoxyz @SecretNetwork @zama_fhe @SunscreenTech @inconetwork @FHEOnchain @Ingo_zk At the same time, ZK-MPC-FHE is still at the research and proof-of-concept stage because when it comes to imposing zero-knowledge, it’s known how to zk-prove one bootstrapping operation but not arbitrary computations (i.e. circuit of arbitrary size). Without ZK, we lose the https://t.co/8tONGlWhlk

Lisa Akselrod (🦑,🪐)

Enclave is beyond the research and proof-of-concept stage. ZK + MPC + FHE. It's real, and it's happening. https://x.com/cryptobuilder_/status/1904823613456294121