nisac
W3B3 || Creator
Latest casts
MPC Preserves privacy in multi-party settings but isn’t very mature. It’s interactive (meaning all users have to send messages back and forth) which makes it difficult to use. FHE The privacy guarantee is similar to TEE, but it can deliver it without any leakholes. It's newer technology and for most use cases in blockchain it would require the assistance of ZK technology for proving integrity. Links to my previous posts on each in the following tweets. THE END
Something I wrote a while back about Privacy and Security and worth repeating Here are the differences between TEE, ZK, MPC and FHE: TEE The aim is to solve integrity and privacy but there is a single point of failure: Physical keys that can be extracted. True, extracting them might be a difficult challenge, but a strong entity with enough resources (think Lazarus Group) combined with a big enough incentive, could do it. TEEss can be used in permissioned settings or on end-user devices for small sums, but should not be used in a decentralized infrastructure. ZK Mature and battle tested. Has been used in production for years by Zcash, StarkWare, and others, with growing acknowledgement by more and more teams. Can provide several versions of privacy while supporting huge (HUGE!) scale. StarkWare created Cairo - a smart contract language designed specifically for ZK.