STON.fi has no formal listing process. Any TON Jetton can be added to the protocol by anyone — you don't need approval from the STON.fi team. The full end-to-end flow looks like this:
1. Deploy your Jetton on TON
Use the standard TON Jetton implementation, or a trusted factory or launchpad. Make sure the metadata — name, symbol, decimals, and logo — is set correctly, because that's what users will see across STON.fi and other tools.
Examples of third-party services that help create a Jetton without writing the contract yourself: minter.ton.org, DYOR, Blum, Stonks.Pump, and other launchpad products in the TON ecosystem.
These are third-party tools, not STON.fi services. STON.fi is not responsible for the operation, security, functionality, or outcomes of using them. Listing them here is not an endorsement.
2. Create a liquidity pool
On STON.fi, go to app.ston.fi/pools and create a new pool — typically a pair with Gram (formerly Toncoin). Detailed walkthrough: How do I create a new liquidity pool on STON.fi?
3. Seed enough liquidity to be useful
A pool with very little liquidity has high price impact and unstable pricing. Aim for an initial contribution large enough that typical swap sizes don't move the price more than a few percent. See Best practices for launching a new pool.
4. Verification (Tonkeeper)
By default, new tokens may appear without verification in third-party wallets such as Tonkeeper. STON.fi itself does not have a verification system. To get the "Unverified Token" status removed in Tonkeeper, submit a Pull Request to the Tonkeeper token-assets repository — see How do I remove the Unverified Token badge in Tonkeeper or Tonviewer?.
5. Announce and direct users to the pool
Share the direct swap link (for example, https://app.ston.fi/swap?ft=TON&tt=YOUR_JETTON_ADDRESS) across your channels. Consider embedding the Omniston Widget on your own site so users can swap without leaving.
If you hit anything unexpected, reach out through the Submit a request form.