How to add a new token on STON.fi
Anyone can add a token to STON.fi by creating a v2 liquidity pool. This guide explains when it’s appropriate, how to do it safely, and how interface policies affect visibility.
STON.fi is permissionless: new tokens become swappable by creating a liquidity pool. This guide walks you through the process, what to check beforehand, and when a token may be hidden in the interface (even if the pool exists on-chain).
When adding a token is appropriate
You’re the token issuer or an authorized contributor.
You’re listing a community token that does not violate IP or impersonate other assets.
The token does not use fee-on-transfer (“tax”) mechanics or you accept that it will be filtered from the UI.
Read more on tax tokens: Tax tokens on TON: what they are and why they aren’t on STON.fi
Step-by-step: add a token by creating a pool
Open STON.fi → Pools → Add liquidity.
In “Provide liquidity,” select the token pair for the pool (e.g., NEW/TON or NEW/USDt). If your token doesn’t appear by name, paste its contract address.
Configure the pool:
Set the initial price by choosing amounts for each side.
Review settings and click Preview pool creation.
Confirm:
Check the popup details (pool parameters, fee from your wallet).
Click Confirm pool creation and approve in your wallet. Pool creation and initial liquidity happen in one transaction.
For the exact click-paths and screenshots, follow guide How to create a new liquidity pool.
After creation
Your pool is live on-chain; swaps can route through it at the protocol level.
If the token is compliant with interface policies, it will appear in app.ston.fi search by name. Otherwise, it may be accessible only by contract address — or hidden/blocked (see below).
Important limits: taxable tokens (fee-on-transfer)
To keep swaps predictable and safe, the STON.fi interface disables “taxable” (fee-on-transfer) tokens. Our AMM/aggregation contracts cannot reliably account for variable transfer deductions across multi-hop routes. What this means for you:
You can still create a pool for a tax token at the protocol level.
However, the token will not be surfaced or routed in app.ston.fi.
Other third-party interfaces may still access the pool directly via the blockchain. Use caution and do your own research.
Important limits: intellectual property and impersonation
Per our Terms of Use, STON.fi hides tokens that:
impersonate known assets (e.g., fake “USDt”, “BTC”),
misuse brands, names, logos, or characters without permission,
claim affiliation with legitimate projects when they are not.
Meme tokens are welcome when they’re original. Direct copies of protected brands are not.
Visibility rules in the interface
Hidden: Some tokens won’t show up by name, but can be used if you enter the contract address manually. Responsibility is on you; verify what you’re adding.
Blacklisted: Fraudulent tokens are blocked entirely in the UI (even by address). These rules affect only the app interface. Pools still exist on-chain and can be accessed programmatically or via other UIs.
FAQ
❓ Can I add a token name/logo? Token metadata is read from the ecosystem’s token registries and community resources. Names/logos may take time to propagate; always share the contract address so users can verify. ❓ Why don’t I see my token by name? It may be new (metadata not propagated), hidden (policy), or filtered (tax token). Users can still paste the contract address if it isn’t blacklisted. ❓ Can I create multiple pools for the same token? Yes, but liquidity fragmentation can worsen swap conditions. It’s usually better to build depth in one or two key pairs (e.g., NEW/TON or NEW/USDt). ❓ Does STON.fi “list” tokens? No approvals are needed at the protocol level. The UI applies safety filters to protect users; the protocol itself remains open and decentralized.
Last updated