> For the complete documentation index, see [llms.txt](https://docs.rujira.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rujira.network/understanding-rujira-history/rujira-and-thorchain.md).

# Rujira & THORChain

Rujira is the App Layer of THORChain, connecting its comprehensive ecosystem of DeFi applications with THORChain’s deep liquidity and cross-chain capabilities. This merger unlocks a powerful synergy, enabling projects to tap into THORChain’s liquidity, native token support, and interoperability while offering a seamless, user-friendly experience for DeFi users.

[RUJI](/understanding-ruji-token.md) will serve as the fee-switch token for the THORChain App Layer, enabling stakers to capture the revenue generated by applications that join the Rujira Alliance, after accounting for the portion shared with THORChain Base Layer to cover security costs.

The standard revenue split between core applications and the Base Layer is 50/50. However, any economic activity that already contributes value to the Base Layer, such as applications built on top of the Rujira primitives, will not be required to pay for security twice.


---

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

```
GET https://docs.rujira.network/understanding-rujira-history/rujira-and-thorchain.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.