> For the complete documentation index, see [llms.txt](https://docs.ellipsis.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ellipsis.finance/dev/list-a-token-with-the-pool-factory/deploying-a-stable-pool.md). # Deploying a Stable Pool Ellipsis offers two types of pools or listings. Listings between tokens that should have the same price between them (a.k.a stable pools), such as BUSD <> USDC <> USDT, and listings for tokens with different prices (a.k.a crypto pools), such as BUSD <> BNB. \ \ Deploy a stable pool on Ellipsis by filling out the [factory form on the website](https://ellipsis.finance/thefactory). Upon submission of the form you will be prompted to complete the transaction. When the transaction is complete, the new pool will be available for seeding the initial liquidity. Once liquidity has been seeded, the pool will appear in the [pools area of the website](https://ellipsis.finance/pool). \ \ Below are instructions for filling out the form. For assistance with the parameters in the form, please get in touch via our [Telegram channel](https://t.me/ellipsisfinance). Pool assets such as going logos for coins that are new to Ellipsis can be submitted as outlined in [Pool Assets](broken://pages/uNgTG25RccdqS2YEBfNu). ### Pool Name and Symbol ![](/files/So119PtyGtelR3qgnk1Z) The name of the pool is what you will see on the [pool listing page](http://ellipsis.finance/pool): ![An example showing the pool names of two fictitious plain pools on Ellipsis. ](/files/veFluOjKL9jEZxwXSyAt) The symbol will be the symbol for your LP token. Typically, metapools use a `{token}3EPS` naming pattern for pools that use the `3EPS` base pool, and `{token}btcEPS` for pools that use the `btcEPS` base pool. ### Pool Type ![](/files/JR1Ids8uXs25wthNI0Vv) Pool type options include `USD` or `BTC` metapools where a token is paired with an Ellipsis base pool, `BNB` native pools for pairing with `BNB` pegged tokens, and plain pools that can accommodate between two to four pegged tokens. ### Pool Tokens ![Here a user is creating a 3EPS metapool and will input their token address to pair it with the Ellipsis 3EPS pool.](/files/s59PyJnBamxZDPOTbPzm) ### Pool Implementation ![](/files/fCgT326WtMSh5SZMkolR) ### Fees and Amplification Parameter ![](/files/LdEvASgzL1KxPQYZjMmr) #### Choosing an Amplification Parameter The amplification co-efficient (“A”) determines a pool’s tolerance for imbalance between the assets within it. A higher value means that trades will incur slippage sooner as the assets within the pool become imbalanced. The appropriate value for A is dependent upon the type of coin being used within the pool. We recommend the following values: * Uncollateralized algorithmic stablecoins: 10 * Non-redeemable, collateralized assets: 100 * Redeemable assets: 200 #### Trade fees EPS pools charge a fee for token exchanges and when adding or removing liquidity in an imbalanced manner. 50% of the fees are given to liquidity providers, 50% are distributed to EPS lockers. For factory pools, the size of the fee is set at deployment. The minimum fee is 0.04% (represented as `4000000`). The maximum fee is 1% (`100000000`). The fee cannot be changed after a pool has been deployed. --- # 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.ellipsis.finance/dev/list-a-token-with-the-pool-factory/deploying-a-stable-pool.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.