> For the complete documentation index, see [llms.txt](https://docs.cruxfinance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cruxfinance.io/token-details/platform-expansion.md).

# Platform Expansion

The goal for this platform is to provide users access to ample resources, ultimately providing a quality of life improvement in their cryptocurrency endeavors. For this reason, the natural course of action for expanding the platform is to integrate wallets and assets from multiple blockchains. To have a platform where one can view an amalgamation of investments, complex financial positions and assets spanning across several blockchains is the aspiration of Crux Finance. Supplying such instruments will impart meaningful benefits to each supported ecosystem.

With the Ergo community's support, we’ll deliver the first iteration of this platform, not only as a proof of concept, but as a vital foundation for the future multi chain platform we envision. 

Any release of tokens from the Platform Expansion allocation will be done so at no greater than a 10% discount to the market rate at that time and must coincide with a cliff and vesting period no shorter than 3 months each.

<br>


---

# 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.cruxfinance.io/token-details/platform-expansion.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.