> For the complete documentation index, see [llms.txt](https://docs.hope.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hope.money/protocols/hopeconnect.md). # HopeConnect HopeConnect is a decentralized asset custody, clearing, and settlement protocol and an essential component of the HOPE Ecosystem. By linking with upper-layer CeFi and TradFi applications through HopeConnect (such as credit card payments, centralized derivative trading, and traditional stock trading), institutional and individual users can collateralize their assets in the vault of the HopeConnect protocol and use the related services through credit from the upper-layer centralized applications. Users can enjoy CEX-level liquidity and trading experience on a decentralized and anonymous protocol with no counterparty risk. HopeConnect acts as a bridge connecting DeFi with CeFi and TradFi, gradually addressing the needs of DeFi users who want to participate in traditional finance. HopeConnect is currently in development and is slated for launch in Q3 2023. --- # 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.hope.money/protocols/hopeconnect.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.