Best practices for launching a new pool

Creating a pool on STON.fi is permissionless and takes minutes — but a poorly seeded pool gives users a bad experience and can quickly attract scam concerns. Here are the practices that tend to separate well-run launches from rough ones.

Seed enough initial liquidity

A small pool means high price impact on every swap, which makes the displayed price look unfair and discourages users. Aim for enough liquidity that a normal-sized swap moves the price by no more than 1–2%.

Pool type

The standard STON.fi user interface lets you create a regular constant-product pool. Other pool types — Stableswap, WCPI, WStableswap — are configured at the protocol level and are not selectable via the standard pool-creation UI. If your token needs a non-standard pool type, submit a request to STON.fi support and we'll route it to the responsible specialists.

Get the token recognized in wallets

While STON.fi itself doesn't verify tokens, the third-party wallets (Tonkeeper, etc.) where most TON users keep their tokens do. Submit your token to Tonkeeper's ton-assets repository as early as possible — by the time you're driving real traffic, the "Unverified Token" badge in Tonkeeper should already be gone. See How do I remove the Unverified Token badge in Tonkeeper or Tonviewer?.

Have a launch communications plan

  • Publish the canonical pool link and contract address on your official channels first, before scammers can.
  • Pin a message warning the community to verify the contract address before swapping.
  • Consider an AMA or a STON.fi community event to coincide with the launch.

Be aware of STON.fi interface warnings and flags

STON.fi applies its own interface-level warnings to tokens that look suspicious — for example, the Honeypot, Fake, Taxable, Blacklisted, and Suspicious flags. Note that the SCAM tag you may see in other TON tools (Tonkeeper, Tonviewer) is not a STON.fi label — it comes from those third-party products. Build credibility through normal token operations, not surprise changes (sudden renames, mass burns, hidden transfer mechanics), so that none of these flags trip on your token.

Was this article helpful?
0

Still have questions? Get in touch

Comments (0)

Please sign in to leave a comment.

Powered by Zendesk