# Security Nodes

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.

<figure><img src="/files/L1rIdS5Uh0OUoNRpktjV" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.mayaprotocol.com/white-paper/readme-1-1/security-nodes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.