> For the complete documentation index, see [llms.txt](https://guide.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.ston.fi/providing-liquidity/how-to-add-a-new-token-on-ston.fi.md). # How to add a new token on STON.fi 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 shown with warnings, restricted, hidden, or blocked in the interface even if the pool exists on-chain. {% hint style="info" %} Before you start: ✅ Ensure you hold enough of both assets to seed the pool. ✅ Review STON.fi interface policies (taxable tokens, IP/impersonation) so you know how visibility works after creation. {% endhint %} ### 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. * If the token uses fee-on-transfer (“tax”) mechanics, you understand that STON.fi does not endorse such tokens and supports them only in limited cases, with user warnings and technical restrictions. Read more on tax tokens: [Tax tokens on TON: what they are and how STON.fi handles them](https://blog.ston.fi/tax-tokens-on-ton-what-they-are-and-why-they-arent-on-ston-fi/) ### Step-by-step: add a token by creating a pool 1. Open STON.fi → Pools → Add liquidity. 2. In “Provide liquidity,” select the token pair for the pool (e.g., NEW/GRAM 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](https://guide.ston.fi/en/providing-liquidity/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 complies with interface policies and technical restrictions, it may appear in [app.ston.fi](https://www.google.com/url?q=http://app.ston.fi\&sa=D\&source=docs\&ust=1778070760205503\&usg=AOvVaw3rZF0cupoqnf_JalCWE0Bb) search by name. Otherwise, it may be accessible only by contract address. #### Why STON.fi labels tokens Labels are used only at the interface level to give users more context before they interact with a token. In other words, labeling is an interface-level transparency tool. Labels are based on observable signals and documented inputs, such as user complaints, manual monitoring, honeypot alerts, and official legal requests. #### Labeled tokens: what it means in practice * Most labeled tokens can only be found by entering the contract address manually. * Fake and Honeypot tokens cannot be swapped in the STON.fi dApp. * Taxable tokens may have limited support, but only under strict technical safeguards. Tokens with transfer tax above 10% are not supported for swaps. * Suspicious and DMCA Notice labels act as warnings; such tokens may still be available in the dApp. * A label does not remove a token from the blockchain. The token still exists onchain and may remain accessible through other interfaces or direct contract interaction. 💡 [Read more on how STON.fi labels non-standard tokens](https://blog.ston.fi/know-what-youre-interacting-with-how-ston-fi-labels-non-standard-tokens/) ### 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](https://ston.fi/terms), 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.
Important limits: taxable tokens (fee-on-transfer) To keep swaps predictable and safe, STON.fi treats taxable tokens as a special-risk category. The interface supports taxable tokens only in limited cases, shows users a clear warning, and applies technical restrictions because transfer deductions can affect received amounts and make routing less predictable. Taxable tokens cannot be used as intermediate assets in routes, and tokens with a transfer tax above 10% are not supported for swaps. * You can still create a pool for a tax token at the protocol level. * However, [app.ston.fi](https://www.google.com/url?q=http://app.ston.fi\&sa=D\&source=docs\&ust=1778065345725201\&usg=AOvVaw2CII-t4NwPBgOcqQ-pKvoH) will handle the token according to its taxable-token rules: the UI will show a warning, the token cannot be used as an intermediate asset in routes, and swaps are not supported if the transfer tax is above 10%. * 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](https://ston.fi/terms), 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.
### 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 because metadata has not propagated yet, hidden by policy, restricted for swaps on STON.fi if it violates safety rules. Users may still be able to paste the contract address. Taxable tokens can still carry warnings and swap restrictions.\ ❓ **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/GRAM 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.