> 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 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.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 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.