> For the complete documentation index, see [llms.txt](https://crosschain-alliance.gitbook.io/hashi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crosschain-alliance.gitbook.io/hashi/core-concepts/additive-security-model.md).

# Additive Security Model

Hashi’s security model is based on **additive security**, where the more oracles involved, the greater the level of protection. This allows developers to dynamically scale the security of their cross-chain interactions by increasing the number of oracles participating in validation.

* **How Additive Security Works**\
  Rather than relying on a single source of truth, Hashi collects validation results from multiple oracles. As more oracles participate in validating block headers and messages, the security of the system increases. This model ensures that even if one or several oracles are compromised, the overall integrity of the system is maintained.
* **Dynamic Security**\
  Developers can adjust the security threshold based on their specific needs. For routine transactions, fewer oracles may be sufficient, but for high-stakes interactions, the number of validating oracles can be increased to ensure maximum security.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://crosschain-alliance.gitbook.io/hashi/core-concepts/additive-security-model.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.