> For the complete documentation index, see [llms.txt](https://docs.fly.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fly.trade/developers.md). # Developers This section serves as a comprehensive guide for developers navigating the fly.trade smart contracts. It aims to provide a detailed walk-through of the protocol's implementation, focusing particularly on cross-chain swaps and on-chain swaps. By delving into the intricacies of these smart contracts, developers will gain a profound understanding of how fly.trade facilitates seamless asset transfers across different blockchain networks. The comprehensive documentation presented here offers insights into the underlying mechanics, logic, and security measures embedded in the cross-chain and on-chain swap functionalities. Armed with this knowledge, developers can confidently engage with and contribute to the fly.trade ecosystem, ensuring a smooth and informed integration of these innovative features into their blockchain applications. --- # 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.fly.trade/developers.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.