> 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/verification-checks.md).

# Verification Checks

The `checks` field on every result is a flat object keyed by check name. For `checkSecretVm`, the relevant set is:

| Check                       | What it proves                                            |
| --------------------------- | --------------------------------------------------------- |
| `cpu_quote_fetched`         | The VM served a CPU quote at `/cpu`                       |
| `tls_cert_fetched`          | The VM's TLS certificate was retrievable                  |
| `cpu_quote_verified`        | Full DCAP / AMD chain verification passed                 |
| `tls_binding_verified`      | `report_data[0:32]` equals SHA-256 of the TLS cert        |
| `gpu_quote_fetched`         | The VM served a GPU quote at `/gpu` (skipped when no GPU) |
| `gpu_quote_verified`        | NVIDIA NRAS verified the GPU attestation                  |
| `gpu_binding_verified`      | `report_data[32:64]` equals the GPU nonce                 |
| `workload_fetched`          | The VM served a `docker-compose.yaml`                     |
| `workload_binding_verified` | The compose hash replays into the measurement             |
| `proof_of_cloud_verified`   | SCRT Labs' parser confirmed the quote (when opted in)     |

The lower-level functions (`checkTdxCpuAttestation`, `checkSevCpuAttestation`, `checkNvidiaGpuAttestation`) emit their own check rows — e.g. TDX has `quote_parsed`, `quote_verified`, `debug_disabled`; SEV-SNP has `report_signature_valid`, `cert_chain_valid`, `crl_signature_valid`, `vcek_matches_report`, `debug_disabled`, `tcb_ordering_valid`.


---

# 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/verification-checks.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.