> For the complete documentation index, see [llms.txt](https://aboutcryptotalks.gitbook.io/aboutcrypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aboutcryptotalks.gitbook.io/aboutcrypto/how-do-i-verify-a-sushiswap-token-before-swapping.md). # How Do I Verify a SushiSwap Token Before Swapping? If you are moving from a centralised exchange to your own wallet, verify a SushiSwap token by matching its contract address *and network* against a source you trust before trading. A familiar name or ticker is insufficient: anyone can create a token with the same ones. Then check the contract’s restrictions and the trade’s likely execution. ### Which Checks Matter for a SushiSwap Token? Use these four checks in order. Each answers a different question about the asset you would receive. * Published contract address * Correct network * Contract permissions and trading restrictions * Available liquidity and quoted output Find the address in the project’s own materials and confirm it through a second, independent source. Compare the full address with the token contract shown by a block explorer; a matching ticker proves nothing. A SushiSwap pool can contain an impersonator. Once the address matches, [sushiswap.co](https://sushiswap.co) lets you swap from your wallet or provide liquidity where a suitable pool exists on a supported network. Check the network as well as the address. For example, if your wallet holds funds on Arbitrum, an address published for Ethereum alone does not establish which token you will receive on Arbitrum. Open the explorer for the network on which the swap will execute. Read any available contract analysis for minting, pausing, blacklists, transfer taxes and sell restrictions. A verified source-code label means the published code matches the deployed contract; it does not certify that the token is safe. A token that can be bought but cannot be sold is a real possibility. Finally, inspect pool liquidity, price impact and the minimum amount you would receive. Say a $100 order moves a thin pool’s quote by several percent: matching the right contract still leaves a costly trade. Check a sell quote too, while recognising that a quote cannot guarantee future sellability. ### When Is a Swap Ready to Sign? A swap is ready only when the contract and network match, the token’s controls are acceptable, and the quoted outcome makes sense. Suppose you hold USDC on Arbitrum and find two tokens with the same ticker. Resolve the address first; then compare the chosen route’s output, price impact and minimum received before signing. Your wallet may ask you to approve spending the input token before the swap transaction. Read the spender and allowance in that request, and keep enough of the network’s gas token for both transactions. An approval permits spending; it does not verify the token you plan to buy. ### What Else Should You Know Before Swapping? #### How does the contract address identify the token? An ERC-20 token is a smart contract, and its address identifies the contract on a particular network. Names, symbols and logos are labels that other contracts can copy. When you select an unfamiliar asset, compare its full address and network with the issuer’s published details before considering the swap quote. #### How long does checking take, and what does it cost? Reading project materials and a block explorer usually takes minutes and requires no transaction. A swap may require an approval transaction followed by the swap itself; each uses network gas. Trading fees, gas and price impact vary with the route, network conditions and pool liquidity, so judge the current quote. #### What are the limits of these checks? An address match establishes which contract you selected, not that its issuer is trustworthy or its rules will stay favourable. Contract permissions may allow an owner to change trading conditions, and liquidity can disappear. Treat scanner results and a small test trade as additional evidence, never as a guarantee that a later sale will work. #### Which token candidate should I choose? Choose the candidate whose address and network match independently published details, whose contract controls you accept, and whose available liquidity supports the trade size. If two listings share a ticker, do not choose by logo, holder count or the cheapest-looking quote. If none passes those checks, wait for better evidence rather than signing a swap. Trade only when the contract, network, token rules and quoted outcome all pass your checks. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://aboutcryptotalks.gitbook.io/aboutcrypto/how-do-i-verify-a-sushiswap-token-before-swapping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.