# Trusted & Untrusted Core

Now that we have a better understanding of how Secret is leveraging SGX, let’s see how the TEE and enclaves works with the Trusted and Untrusted cores.

## **Untrusted Core**

* Responsible for running the Cosmos SDK and Tendermint.
* Contains code for creating and managing the enclave (load and destroy).
* Can call the CosmWasm module and kick off Secret Contract execution within the enclave.

## **Trusted Core**

* Responsible for executing Secret Contracts.
* Responsible for SGX-specific mechanisms: Remote Attestation and Sealing.
* Able to make read/write calls from the Tendermint state at any point during execution.
* The enclave only stores the seed. The enclave may also store the local node's key pair.

> **Note:** During contract execution, only the state of the contract being executed can be changed. Other contracts can be queried (i.e. run code that can't change the state of another contract) synchronously, but calls to other contracts and requests for transactions can only be queued. Those operations will happen after the contract has finished running. This is intentional as it prevents a lot of bugs, like the re-entrancy bugs plaguing Ethereum.

Below is a diagram of how the Untrusted and Trusted behave on a User transaction and Secret Contract execution:

![Trusted Execution Environments on Secret Network.](https://lh4.googleusercontent.com/J5WogjAXu-51NfKv8EYRA2RcOBTvuW2AboiYWrYTFM8mErrPYy59zDuA3Sx9R3Kav6OtirLDXJgeLUj87zCnQWeNDJExpX6bkWrUpquJeljfOuUQjwrU4B0U3cD-7_c9actUbLcf65cIeEz1ow)

\\


---

# 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.scrt.network/secret-network-documentation/introduction/secret-network-techstack/privacy-technology/intel-sgx/trusted-core.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.