> For the complete documentation index, see [llms.txt](https://stargateprotocol.gitbook.io/stargate/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stargateprotocol.gitbook.io/stargate/v2-developer-docs/integrate-with-stargate/how-to-list-your-token-on-stargate.md). # How to List Your Token on Stargate ## OFT Stargate will list any OFT that requests a listing, as mandated by the DAO in [this vote](https://snapshot.org/#/stgdao.eth/proposal/0x00b8f2f79d105b9c2da9a346a24ff7c9f1295d4760e11e93709d4e5f0165c2ef). As part of this vote, every transfer through Stargate will also be subject to a 2bps (0.02%) fee. \ \ Please fill out [this form](http://tinyurl.com/stargate-oftlisting) with all relevant information regarding your OFT. There are 3 requirements for an OFT to be listed on Stargate's FE; 1\) The token must be live on either CoinMarketCap or CoinGecko for pricing.\ \ 2\) Additionally, every pathway MUST have `enforcedOptions` set. You can read more about this in [LayerZero's documentation](https://docs.layerzero.network/v2/developers/evm/oft/quickstart#setting-enforced-options). Specifically, you must specify `enforcedOptions`for `lzReceive` `msgType` 1. A typical OFT's `lzReceive` call will use `60000` gas on most EVM chains, so you can enforce this option to require callers to pay a `60000` gas limit in the source chain transaction to prevent out of gas issues: ``` _options = 0x0003010011010000000000000000000000000000ea60; ``` \ 3\) (soft-requirement) It is required that the networks where the OFTs are deployed are fully interconnected (full-mesh). For example, if your OFT contracts are deployed on networks A, B, and C, ensure the following pathways are active: `A<>B` ; `B<>C` ; `A<>C` . If your OFT meets the above 3 requirements, you can fill out the form at: For Solana OFTs, please share the following addresses in the form: \ { "programId": "", "mint": "", "mintAuthority": "", "escrow": "", "oftStore": "" } ## Hydra (OFTs) [Hydra](/stargate/v2-developer-docs/integrate-with-stargate/token-types/hydra-ofts.md) operates on a foundational principle where Stargate's core pools, residing on chains with native assets (e.g., Ethereum, Arbitrum, Optimism), are leveraged to facilitate asset bridging to newer chains lacking native assets. The Hydra supported assets are OFTs. If you would like to enable the Hydra supports for your chain, you should contact the Stargate Foundation to facilitate the deployment. ## APD - Autonomous Pool Deployment If your token is not using OFT standard, you can still have it listed on Stargate. To do this, start by submitting a proposal on Commonwealth by following the instructions provided in [this guide](https://commonwealth.im/stargatetoken/discussion/5085-apd-autonomous-pool-deployment). Your proposal must undergo and pass the governance process, including receiving community approval through votes on Snapshot.\ \ After approval, you are required to provide the specified liquidity for each pool as outlined in your proposal. Furthermore, if your proposal includes incentive programs, you should implement these as well. Lastly, you will be responsible for managing the pools, specifically rebalancing them when liquidity in certain pathways runs low, which could impact users' ability to bridge tokens. --- # 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://stargateprotocol.gitbook.io/stargate/v2-developer-docs/integrate-with-stargate/how-to-list-your-token-on-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.