> For the complete documentation index, see [llms.txt](https://docs.kyberswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyberswap.com/getting-started/foundational-topics/decentralized-technologies.md). # Decentralized Technologies Without Which None Of This Would Be Possible There are a whole range of decentralized technologies which makes what we do here at KyberSwap possible. As our focus lies in making decentralized swaps accessible to all, we realized early on that KyberSwap will be able to generate the most value-add for users at the decentralized application layer. Consequently, we have decided to leverage the expertise of various decentralized infrastucture providers by integrating and building on top of their respective ecosystems. Critically, this process of integration is contingent upon KyberSwap maintaining its open and permissionless nature. To this end, the sections below outlines some of the key decentralized technology topics where significant consideration was required when designing KyberSwap solutions. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kyberswap.com/getting-started/foundational-topics/decentralized-technologies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.