> For the complete documentation index, see [llms.txt](https://astralecosystem.gitbook.io/astralecosystemwhitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://astralecosystem.gitbook.io/astralecosystemwhitepaper/astral-ecosystem-2.0/conclusion.md).

# CONCLUSION

No doubt, DeFi is the most proper concept for the spirit and purpose of cryptocurrencies and blockchain. Considering the open-source nature of the decentralized blockchain world, it is an inevitable outcome that all innovations are public and continue as an endless loop. This is why the DeFi technology of 2020 has evolved to DeFi 2.0. Obviously, the recent liquidity crises have played an important role in this evolution. Naturally, it can be assumed that a single mainnet or approach will no longer be sufficient for a disruptive technology like DeFi/blockchain. Therefore, the operation of projects building with products connected only to a single mainnet would be contrary to the evolutionary spirit of the blockchain. Astral Ecosystem will offer SHROOM token holders a chance to gain different earnings with its fair economic design. As a result of the inevitable nature of evolution as well as its flexible and well-designed mathematical infrastructure, Astral Ecosystem would easily keep up with potential evolutions in the future.


---

# 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://astralecosystem.gitbook.io/astralecosystemwhitepaper/astral-ecosystem-2.0/conclusion.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.
