> For the complete documentation index, see [llms.txt](https://docs.mayaprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mayaprotocol.com/white-paper/readme-1-1/security-nodes.md).
# Security Nodes
Exporting security to other Application-Specific-Blockchains and creating a Maya Economy.
Maya Protocol is designed to be safe, useful, and solvent to attract Liquidity Providers and facilitate cross-chain exchanges. Due to its economical design and incentives, it has the ability to export this Security and Solvency to other listed chains while sharing $CACAO tokens. Maya can remain a conservative space even though $CACAO can be used in other, more flexible, or fast-growing environments, creating new use cases and demand for it while bringing back more economic activity to the Maya Economy.
### ELI5
1. Maya is, by design, a very solvent, very secure, and very censorship-resistant network. It also has the tradeoff of not supporting some interesting capabilities like smart contracts, DeFi, derivative products, NFTs, etc.
2. Maya could export its security and solvency architecture to other side chains by sharing the same nodes and the same native token —$CACAO. This can be accomplished with triple redundancy by having an IBC bridge, Bifröst equivalent —and what we call a “Security Nodes” model. In exchange for securing alternative chains, Maya Protocol can earn fees or taxes differently.
3. Alternative chains could have many functionalities and economic activities that benefit $CACAO and the whole Maya ecosystem. As long as it is done within certain limits and parameters, there is little to no downside in having more chains.
---
# 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.mayaprotocol.com/white-paper/readme-1-1/security-nodes.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.
