> For the complete documentation index, see [llms.txt](https://docs.nomad.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nomad.xyz/the-nomad-protocol/security/root-of-trust.md).

# Root of Trust

The root of trust is the lynchpin of an interoperability protocol's security. As the name suggests, it lies at the heart of the system — any trust assumptions are only as strong as the root of trust itself.

Nomad's [optimistic verification](/the-nomad-protocol/verification-mechanisms/optimistic-verification.md) mechanism is its root of trust. The mechanism ensures that state is not corrupted, and must be bulletproof for any application building on top of Nomad.

There are two primary components when it comes to Nomad's root of trust security:

1. [**Fraud Detection**](/the-nomad-protocol/security/root-of-trust/fraud.md) — Nomad enables Watchers to monitor the system and flag fraud if they detect anything abnormal. Nomad **requires only one honest** **Watcher** to maintain liveness to protect the system. This ensures that malicious Updaters are not able to confirm corrupt messages within Nomad.
2. [**App-Governed Root of Trust**](/the-nomad-protocol/security/root-of-trust/app-governed-root-of-trust.md) — Unlike other cross-chain messaging systems that offer monolithic security for all applications, Nomad enables application governance to decide which Watchers they permit to flag fraud and notify their application on-chain.

This section and its associated pages will break down the various components of Nomad's root of trust including:

* How fraud is prevented with the optimistic mechanism
* Why application governed root of trust returns consent to users
* Inherent liveness and economic security assumptions of optimistic verification


---

# 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.nomad.xyz/the-nomad-protocol/security/root-of-trust.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.