6 Contract Decisions That Make a Token Hard to Trade (That Nobody Warns You About)

Frequently Asked Questions

01.What is the right total supply for a token?

There's no universal answer, but there is a method. Work backwards from the unit price you expect to trade at, then check the minimum tick size your target venues use in that range. A token priced far below the venue's smallest increment has a spread that can't be tight in percentage terms, however much depth is resting in the book.

02.Do anti-whale limits hurt liquidity?

Usually yes, and more than teams expect. A max wallet cap applies to exchange hot wallets and Market Maker inventory as well as to whales. A cap low enough to matter is normally low enough to break deposit sweeps, or to force inventory across several addresses. The setting that deters bots and the setting that blocks a working book aren't always the same number, but they're close enough that the trade-off has to be deliberate.

03.Why does chain choice affect spreads?

Because depth doesn't move between exchanges by itself. Rebalancing across venues takes as long as the chain takes to settle, and capital in transit isn't resting in a book. Slower settlement means either more capital committed per venue or less depth quoted on each. It also means price gaps between venues stay open longer.

04.Can any of these be fixed after launch?

Caps and cooldowns can, if the contract allows it and the keys still exist. A pool fee tier can be worked around by deploying a new pool and migrating liquidity, at the cost of splitting it during the move. Total supply, decimals and chain can't change without a migration, which means asking every holder and every integration to move with you.

05.Which of these six get flagged in an audit?

The settings themselves rarely are. What gets flagged is the admin role behind caps, cooldowns and launch gating, because a key that can exempt addresses or switch trading on and off is centralization risk. Any contract that does math on the token still gets its rounding tested at the edges of the price range it will trade in.

06.When in the build should these be decided?

Before the code freezes for audit, ideally in the same weeks the tokenomics are drafted, because supply, decimals, chain and pool tier can't change later without a migration or a new pool. Caps and cooldowns can be tuned closer to launch, but only if the ability to raise or remove them is already in the audited code.