> For the complete documentation index, see [llms.txt](https://docs.portaldefi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.portaldefi.com/use-cases.md). # Use Cases Portal’s Notary Chain is a highly customized application specific chain built to support fast and cheap transaction recordings to enable swaps. However, the primitives on native chains and the coordinator can support multiple use cases. Some of the potential use cases are explored below: * Non-custodial Peer-Peer Swaps * AMMs on Cross-Chains * Multi-chain money market aggregation - Users can stake a token as collateral on chain A and borrow an asset on chain B. * Cross-chain composability leads to complex use cases by plugging contracts on chain A with chain B. * Seamless swapping of gaming assets between different gaming platforms that use various blockchains. * Inter communication between blockchains and AI related platforms to prove model provenance. * Cross-chain Governance * Option Contracts on Bitcoin/Lightning network * Escrow service on Lightning network * Off-chain smart contracts on Lightning network using Portals Bitcoin L3. Portal Network is launching with the first 2 products described above (P2P swaps, AMM swaps) but expect developers to take advantage of the SDK in building advanced 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.portaldefi.com/use-cases.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.