# How Lumoz TEE Works

Lumoz aims to be the core processing platform for AI computation, playing a critical role in supporting scalable blockchain infrastructure. By integrating Trusted Execution Environment (TEE) technology, Lumoz ensures the security and transparency of its computational processes.

This innovative combination merges the decentralization strengths of blockchain with the robust security of TEE, enabling Lumoz to deliver not only a decentralized cloud computing network but also the ability to efficiently execute various computational tasks in a trust-minimized environment.

<figure><img src="/files/3FeB7Yguz5XR87sJgZ1L" alt=""><figcaption></figcaption></figure>

#### Benefits of Introducing TEE <a href="#heading-benefits-of-introducing-tee" id="heading-benefits-of-introducing-tee"></a>

* Hardware-Level Security: The secure hardware enclave ensures privacy, confidentiality, and data integrity.
* No Computational Overhead: Applications running in TEE operate at nearly the same speed as those in a standard CPU environment.
* Low Verification Costs: Verifying TEE proofs consumes minimal gas, requiring only ECDSA verification.

#### TEE Implementation Outcomes <a href="#heading-tee-implementation-outcomes" id="heading-tee-implementation-outcomes"></a>

* Tamper-Proof Data: Ensures that user request/response data cannot be altered by intermediaries. This requires secure communication channels and robust encryption mechanisms.
* Secure Execution Environment: Both hardware and software must be protected from attacks, leveraging TEE to create an isolated environment for secure computation.
* Open-Source and Reproducible Versions: The entire software stack, from the operating system to application code, must be reproducible. This allows auditors to verify the system's integrity.
* Verifiable Execution Results: AI computation results must be verifiable to ensure that outputs are trustworthy and untampered.

#### **TEE (Intel SGX) Framework** <a href="#heading-tee-intel-sgx-framework" id="heading-tee-intel-sgx-framework"></a>

<figure><img src="/files/aRPViALqQ5KOT8UzmpZf" alt=""><figcaption></figcaption></figure>

#### TEE Server Security Verification <a href="#heading-tee-server-security-verification" id="heading-tee-server-security-verification"></a>

When the service starts, it generates a signing key within the TEE.

1. You can obtain CPU and GPU attestations to verify that the service is running within a confidential VM in TEE mode.
2. The attestation includes the public key of the signing key, proving that the key was generated within the TEE.
3. All inference results are signed using the signing key.
4. You can use the public key to verify that all inference results were generated within the TEE.

### **TEE and ZK Multi-Proof** <a href="#heading-tee-and-zk-multi-proof" id="heading-tee-and-zk-multi-proof"></a>

No single cryptographic system can be guaranteed to be 100% secure. While current Zero-Knowledge (ZK) solutions are theoretically secure, they cannot ensure flawless operation across the entire system, especially from an engineering perspective, given the complexity of ZK implementations.

This is where multi-proof systems come into play. To mitigate potential errors in ZK implementations, hardware-based solutions like Trusted Execution Environments (TEE) can act as a dual-factor verifier, providing an additional layer of security for ZK-based projects such as AI Agents.

<figure><img src="/files/N15lJfjruWwwQB3UWv98" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lumoz.org/ai-agents/how-lumoz-tee-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.