> For the complete documentation index, see [llms.txt](https://liquidx-3.gitbook.io/liquidx-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://liquidx-3.gitbook.io/liquidx-whitepaper/3.-problem-statement/3.1-the-gap-in-the-eon-ecosystem.md).

# 3.1  The Gap in the EON Ecosystem

The EON blockchain is a capable, fast, and cost-efficient blockchain infrastructure. However, it currently lacks the DeFi applications that would make it a fully functional financial ecosystem. This is not unusual - most blockchains begin as bare infrastructure and acquire DeFi layers over time. Ethereum, for example, had no DeFi protocols until years after its launch.

The current limitations on EON are straightforward: EON token holders can stake their tokens for basic rewards, but they have no way to use their holdings productively. There is no lending platform, no yield optimization, and no way to access liquidity without selling assets. This is the gap LiquidX fills.

<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://liquidx-3.gitbook.io/liquidx-whitepaper/3.-problem-statement/3.1-the-gap-in-the-eon-ecosystem.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.
