> For the complete documentation index, see [llms.txt](https://docs.unizen.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unizen.io/introduction-to-unizen/unizen-overview/unizen-interoperability-protocol-uip/stargate.md). # Stargate Stargate Finance is, pretty much, a native asset bridge, with a focus on stablecoins.. As a liquidity transport protocol, the platform allows users to add liquidity to various pools, stake assets, and transfer native assets - which reduce the risk of losing a substantial sum of money since their price is pegged to a stable asset. Even though Stargate Finance was started by LayerZero Labs, it's considered to be a community-driven project. In fact, the exchange aims to provide users with total transparency with documents and white papers that address any potential issues. Users also can earn high returns with unified liquidity pools as well as extensive farming features. Stargate is the first bridge to solve the bridging trilemma. Existing bridges are forced to make trade-offs on the following core bridge features: * **Instant Guaranteed Finality:** Users & Applications can trust that when they successfully commit a transaction on the source chain, it will arrive on the destination chain. * **Native Assets:** Users & Applications swap in native assets as opposed to wrapped assets that require additional swaps to acquire the desired asset and corresponding fees. * **Unified Liquidity:** Shared access of a single liquidity pool across multiple chains creates deeper liquidity for users & applications that trust in the bridge's reliability. --- # 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.unizen.io/introduction-to-unizen/unizen-overview/unizen-interoperability-protocol-uip/stargate.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.