> For the complete documentation index, see [llms.txt](https://docs.ecko.finance/eckodao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecko.finance/eckodao/eckodex/eckodex-litepaper/why-eckodex/solution-decentralised-infrastructure.md). # Solution: Decentralised Infrastructure eckoDEX believes in the true vision of DeFi: decentralise everything and open to all. From liquidity provisioning and pricing to swapping, to ownership and organization, to websites and front-ends - if it can be run on-chain, it is; if it can’t, then we ensure there is no central authority or service. This idea is often brought to the very edge with not actually going all the way, with DEXes maintaining control of their interface and centrally hosting their website and front-end. Not eckoDEX. From our website and front end being supported by Flux, to everything in our eckoDEX code being owned by the DAO, we are DeFi. --- # 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.ecko.finance/eckodao/eckodex/eckodex-litepaper/why-eckodex/solution-decentralised-infrastructure.md?ask=&goal= ``` `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.