TEE and ZK have a key difference: TEE requires a third-party trust.

Written by: Haotian

Recently, there has been extensive discussion around the differences between ZK and Trusted Execution Environments (TEE). The reason is that the newly entered layer2, @unichain, claims its millisecond sub-blocks are built on TEE, while the oracle old chain @FlareNetworks, which claims to be a data blockchain, integrates traditional internet channels like Google Cloud to introduce verifiable off-chain computation through TEE. Combining these two points, here are my thoughts:

1) TEE (Trusted Execution Environment) is a hardware-level security technology. In simple terms, TEE creates an independent, secure, and isolated enclave environment within the processor, completely isolated from the main operating system programs, allowing for the secure storage and protection of sensitive data, while having strict access control mechanisms.

This means that developers can execute specific programs within TEE, fully amplifying the hardware's execution efficiency and performance while ensuring security. Currently, there are various implementations of TEE, including Intel SGX and ARM TrustZone, which have broader applications in mobile internet, IoT, and other fields, with applications in blockchain scenarios being explored.

2) Unichain, based on the TEE environment, allows transactions to be pre-executed and verified before they are officially packaged into blocks. This breaks the previous limitation of transactions uniformly uploading to the Mempool and waiting to be packaged, while also providing a relatively secure and closed environment against tampering, thus making it possible.

Flare Network's approach to being an oracle is also amplified by leveraging the TEE environment. Feeding price indicators purely for DeFi contract environments can be very competitive; however, if the data scope is expanded to include sports results, social media data, real-time election rankings, etc., it requires substantial off-chain computation and processing power, ultimately passing the verifiable results back to the on-chain environment.

Flare will conduct intensive computational operations through the TEE environment provided by Google Cloud, only feeding trusted results onto the chain, avoiding the large costs associated with accumulating vast data sources on-chain. The idea is simple: complex computational tasks are executed off-chain, and then verified on-chain through brief proofs, which can reduce the data load and computational demands on-chain.

3) After making comparisons, it is not difficult to find that the TEE Trusted Execution Environment, to some extent, relies on hardware manufacturers (such as AMD and Intel) combined with traditional upstream service providers like Google Cloud to provide "trustworthiness," performing a pre-processing step on the original data before applying the data results to the chain. This has a key difference from ZK, which relies on mathematical principles and cryptographic algorithms without depending on any hardware for trust: TEE requires a third-party trust.

How can this issue be resolved? The logic is also simple: TEE + verifiable Prove network. Introducing a verifiable proof network can significantly enhance the transparency and credibility of the TEE system. The decentralized verification network that Unichain aims to introduce, along with the distributed node governance architecture provided by Flare's blockchain framework, serves as this verification network.

Although Unichain has not yet revealed the implementation and governance details of this verification network, how to utilize the remote verifiable characteristics of the TEE enclave environment and how to generate proofs while ensuring security and confidentiality through hardware to interact with the on-chain environment will certainly be key points.

免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。