> For the complete documentation index, see [llms.txt](https://docs.scrt.network/secret-network-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/verifying-a-secretvm/secretvm-verify-sdk/trust-model.md).

# Trust Model

Verification is only as strong as what the SDK trusts. The chain is:

* **Intel SGX Root CA** — pinned in code; collateral is fetched from PCCS over HTTPS but the chain is anchored locally.
* **AMD ARK** — pinned per product (Milan, Genoa, Turin) by SHA-256 of its `SubjectPublicKeyInfo`; HTTPS to `kdsintf.amd.com` is **not** load-bearing for trust.
* **NVIDIA NRAS JWKS** — JWT signatures are verified against NVIDIA's published JWKS. The NRAS root CA is **not** currently pinned (NVIDIA does not publish it); the JWKS is trusted via HTTPS.
* **SecretVM registry** — bundled with each release and refreshed from `github.com/scrtlabs/secretvm-verify` on a miss. Refresh content is trusted via HTTPS to GitHub.

The SDK does **not** trust the VM itself, the operator, or the network path beyond what these roots permit.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/verifying-a-secretvm/secretvm-verify-sdk/trust-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.