> For the complete documentation index, see [llms.txt](https://docs.ra.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ra.exchange/introduction-to-ra/what-is-ra/why-fraxtal.md).

# Why Fraxtal?

<figure><img src="/files/dVBQIeCAbsNaae6Ogdxi" alt="" width="563"><figcaption></figcaption></figure>

RA has chosen to deploy on Fraxtal given our successful, mutually beneficial, relationship on RAMSES and other related forks. The Frax team has always been trailblazers in the space, and shares the same ethos as us. Fraxtal is an opportunity to collaborate further and expand the reach of the Frax ecosystem.&#x20;

Fraxtal has unique features not live on other Layer 2s at the time which also allure builders such as ourselves. For example, sequencer revenue is shared to transaction callers and smart contracts-- effectively promoting the usage of blockspace. The native gas of frxETH allows frax's operations to exponentiate their growth as well; a very intuitive design choice.


---

# 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.ra.exchange/introduction-to-ra/what-is-ra/why-fraxtal.md?ask=<question>&goal=<endgoal>
```

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