> For the complete documentation index, see [llms.txt](https://docs.openpeer.xyz/openpeer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openpeer.xyz/openpeer-docs/openpeer-protocol/roadmap.md). # Roadmap OpenPeer's goal is to build a fully decentralised and self-custodial peer-to-peer exchange protocol for users to connect and trade between crypto and fiat. Our core team and contributors are working on various projects towards this goal. This is a brief overview of some of the projects we're working on or plan to in the near future. ### Q4 2023 * Tron and Solana Support ### Q1 2024 * Mobile Wallet SDKs * Reputation and Reviews ### Q2 2024 * Native Banking Integrations * Fiat Transfer Verification and Automation ### Future * Multi-chain and Any Token Settlement * Decentralised Arbitration * Localised DID integrations * Decentralised Reputation *The Roadmap is constantly evolving and subject to change* --- # 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.openpeer.xyz/openpeer-docs/openpeer-protocol/roadmap.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.