> For the complete documentation index, see [llms.txt](https://crosswise.gitbook.io/crosswise-litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crosswise.gitbook.io/crosswise-litepaper/introduction.md). # Introduction The internet boomed once barriers to entry were significantly reduced. From domain names to hosting and payment providers, as key technologies became sufficiently accessible and integrated, a creative wave was unleashed. Similarly, today’s blockchain and crypto world resembles an island archipelago, with numerous disparate ecosystem “islands”. Fragmented, lacking in security, difficult to scale and synchronize, the crypto world needs greater integration and interoperability to achieve mass adoption. Crosswise intends to be a driving force contributing to these integration efforts in the DeFi space, by bridging the gap between centralized and decentralized exchanges. Our goal is for a user experience that combines the best of both worlds. Tighter security, cross-chain transactions, gasless swaps, verified listings and the right tools. All tightly integrated and easy to use. --- # 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://crosswise.gitbook.io/crosswise-litepaper/introduction.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.