> For the complete documentation index, see [llms.txt](https://docs.saga.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saga.xyz/introduction/saga-overview/saga-shared-security.md).
# Saga Shared Security
One of the challenges of deploying a Cosmos-based application specific chain is the complexity around securing the chain. Each application chain requires gathering validators, distributing staking tokens and designing a token mechanism that helps secure the chain. Saga uses shared security to remove this barrier to entry. Every Saga Chainlet is secured by the Saga Mainnet validators using shared security.
There are many flavors of shared security. Saga uses a model similar to the Cosmos Hub’s version 1 interchain staking called Optimistic Coordination to ensure security of each of the Chainlets.
* Every validator on the Saga Mainnet is required to validate every Chainlet provisioned
* Validators agree on a set of SLA for Chainlet provisioning and maintenance such as timely deployments, guaranteed compute capacity, minimum uptime, honest consensus participation, and inter-blockchain communication relaying
* An auditor monitors the Chainlet and creates a governance case in the event that a validator fails to meet service obligations
* Saga Mainnet enforces any consequences needed for validators violating SLA
With Optimistic Coordination, Chainlets automatically inherit the security of the Saga Mainnet. However, to make provisioning Chainlets as simple as possible, Saga requires a suite of tools to facilitate Chainlet orchestration for validators.
---
# 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://docs.saga.xyz/introduction/saga-overview/saga-shared-security.md?ask=&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.
