> 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/disclaimer.md).

# DISCLAIMER

<figure><img src="/files/Tq7mtYBv9AQfU9WXRlqC" alt="" width="375"><figcaption></figcaption></figure>

The information contained in this Whitepaper is provided solely for informational and educational purposes and may be subject to modification, revision, or updates without prior notice. Nothing in this document shall be interpreted as a commitment, guarantee, representation, or warranty by LiquidX, the community, contributors, developers, or any associated individuals regarding the future availability, functionality, performance, or value of the LiquidX protocol or the LQX token.

This Whitepaper does not constitute, and should not be construed as, an offer to sell, a solicitation to buy, or a recommendation for any securities, financial instruments, or investment products in any jurisdiction. Participation in decentralized finance (DeFi), blockchain protocols, and digital assets involves substantial risk, including but not limited to market volatility, smart contract vulnerabilities, regulatory uncertainty, liquidity risks, and the potential loss of capital.

LiquidX is a decentralized protocol operating through autonomous smart contracts on the EON blockchain. The protocol is community governed and is not operated as a traditional centralized company or financial institution. No statements within this document should be interpreted as legal, financial, tax, or investment advice. Users and participants are strongly encouraged to conduct their own independent research (“DYOR”) and consult qualified legal, financial, and tax professionals before engaging with the protocol or acquiring any digital assets.

While reasonable efforts have been made to ensure the accuracy and reliability of the information presented, all content is provided “as is” without warranties of any kind, whether express or implied. Market data, projections, protocol metrics, token values, yield estimates, and other forward-looking statements are based on assumptions, expectations, and publicly available information that may change over time and may not prove to be accurate.

Certain statements contained in this Whitepaper may constitute forward-looking statements, including but not limited to protocol development plans, roadmap objectives, token utility, governance implementation, ecosystem growth, future integrations, projected yields, and adoption expectations. These statements involve known and unknown risks, uncertainties, and external factors beyond the control of LiquidX and may cause actual outcomes to differ materially from those expressed or implied.

Visual elements including graphics, diagrams, charts, tokenomics illustrations, and ecosystem representations are intended solely for conceptual and informational purposes and should not be relied upon as definitive financial or operational guarantees.

By accessing, reviewing, or relying upon this Whitepaper, the reader acknowledges and accepts all associated risks related to blockchain technology, decentralized finance, and digital asset participation.


---

# 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/disclaimer.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.