> For the complete documentation index, see [llms.txt](https://arenaplay-os.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arenaplay-os.gitbook.io/untitled/arenaplays-solution.md).

# ArenaPlay's Solution

MUSD "Stability Points"

APC tokens are the base currency in the ArenaPlay ecosystem. However, MUSD will be established as a stable coin to be used in various games and competitions within the Arenaplay Ecosystem. Users will be able to exchange APC for MUSD and vice versa at any time. APC will act as gold for the ecosystem and can therefore be easily used without any third party settlement institution international trade.

Banks, market makers, liquidity providers, etc. are connected to ArenaPlay as gateways, whose main role is to bring real national currencies into the ArenaPlay cross-border trade payment network.

Role 2: Customer

Customers within ArenaPlay will not just be the average user but also include: consumer companies, cross-border trade payment solutions etc. If a party doesn’t confirm a transaction during the transaction process it will not be validated. This joint verification greatly avoids the risk of opaque information.


---

# 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://arenaplay-os.gitbook.io/untitled/arenaplays-solution.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.