The moment to stop treating a swap as a two-button task is when the quote looks fine, you hit confirm, and then notice the token you bought is not the token you meant to buy. The ticker matched. The logo looked close enough. Your wallet is connected, you have used a DEX before, and suddenly the easy part has already happened while the important check did not.
That was the decision point with SpookySwap: use the familiar route—search a name, pick the first result, accept the default settings—or slow down for the one detail that remains useful after you know how to connect a wallet. On Sonic, the network is chain ID 146, but being on the right network does not establish that a token is the right contract. For the actual SpookySwap route and its trading interface, I keep spookyswap.dev handy; the point is to arrive with the contract-address question already settled, not to improvise it in the token picker.
The mistake is understandable because familiar assets are easy to recognize by symbol. “USDC” feels like a complete instruction. On a permissionless chain it is not. A token name is metadata someone chose; the contract address is the thing the swap will actually interact with. Those two facts only need to diverge once for the lesson to become expensive.
The check that changes the trade
For an established asset, copy the contract address from the asset’s official project page or a trusted reference you already use, then paste that address into the selector. Do this before entering the amount. It takes perhaps ten seconds, and it changes the question from “does this look right?” to “does this exact address match the asset I intended to trade?”
The options on the table are usually less dramatic than people make them:
- Search by name when you are trading a token you already hold and the wallet has identified it consistently.
- Paste the address when the token is new, bridged, thinly traded, or simply unfamiliar.
- Walk away when you cannot find a primary source that publishes the address clearly.
The third option is the one that felt overly cautious at first. Hindsight says it is mostly efficient. There will be another pool, another route, another time to trade. There is no upside to being the person who discovers after settlement that a cloned ticker had liquidity.
Once the address is confirmed, then review the quote. Price impact and slippage are different problems: price impact is what your size does to the pool’s price; slippage is the maximum worse execution you allow while the transaction is pending. A tiny trade in a deep pool can make both uninteresting. A larger trade or a sparse pool can make either one the entire trade.
What I would do differently on the first swap
I would split the first unfamiliar route into two transactions. First, make a deliberately small swap. Then inspect what lands in the wallet: contract, balance, and whether the token appears where it should. The second swap is no longer an experiment. It is just a trade.
That approach also reveals whether the route behaves as expected without turning a settings screen into a ritual. You do not need to set an exotic slippage number because someone posted one in a chat. You need to understand what the quote is promising and decline it if the minimum received is not acceptable.
SpookySwap is most useful when the convenience of a fast Sonic swap does not encourage a rushed choice. Connect on the intended network, keep enough S for the transaction, paste the contract address for anything you would not recognize on-chain, and read the quote once before signing. That is the whole routine. It is short enough to use every time, which is why it is the one worth keeping.