Before signing a ParaSwap swap, verify the token address, the spending permission, and the exact transaction effect—not just the token symbol or quoted output. An approval can be a separate on-chain permission from the swap itself, and a mistaken approval may remain usable after the trade is abandoned. The practical goal is simple: authorize only the asset and amount you intend to use, then confirm the swap matches the quote you accepted.
Why a token approval deserves its own review
Most ERC-20 tokens require an allowance before a contract can transfer them from a wallet. That allowance is not a payment; it is permission for a specified spender to move up to a specified amount of that token. A wallet may therefore present two requests: one to approve spending and another to execute the exchange.
The risky moment is when the approval screen is treated as routine. Token tickers are not unique, and a familiar-looking symbol does not prove that the contract is the asset you meant to trade. An unlimited allowance also has a different risk profile from an allowance equal to the proposed input amount: it remains available until it is changed or revoked.
For a one-off or unfamiliar asset, use the contract address from a source you already trust, such as the asset issuer, your wallet’s verified token list, or a record you previously checked. Match the full address on the selected network. Do not rely on a search result, a chat message, or a copied ticker alone.
Check the approval request in this order
- Confirm the network. The wallet network must be the one holding the input asset. The same ticker can represent different tokens on different networks.
- Confirm the token contract. Compare the address character for character with your trusted reference. If the wallet shows only a symbol, open the contract details before proceeding.
- Read the spender field. An approval authorizes a particular contract address, not a generic application name. Make sure the wallet is showing the expected transaction context and that you did not arrive through an untrusted lookalike site.
- Check the allowance amount. Prefer an amount close to the intended input for a trade you do not expect to repeat. If choosing a larger allowance for convenience, make that a deliberate decision.
- Separate approval from exchange. A successful approval does not mean the swap has happened. Wait for the approval to confirm, then review the later swap request independently.
A useful decision rule is to stop if two identifiers disagree: the network, token address, spender, recipient, or amount. A quote that appears attractive does not compensate for an unresolved identity mismatch.
Review the swap after the approval, not before it
Once an approval is complete, refresh the quote rather than assuming the earlier output remains available. On-chain prices, liquidity, gas conditions, and route availability can change while the approval is being confirmed. The final transaction should still show the intended input token, input amount, and a minimum amount of output that you can accept.
If you need to understand the terminology used around this review step, consult the ParaSwap transaction checks relevant to the route and transaction you are preparing. Then return to the wallet request and compare its token addresses and amounts against your own intended trade.
That comparison cannot establish that an asset is legitimate or that its price will remain stable. It only helps confirm that the transaction is technically aligned with the trade you chose to make.
Know what a transaction preview can and cannot prove
Wallet simulations and transaction previews are valuable because they can reveal the expected token movements before signing. Treat them as a final consistency check: your input balance should decrease by the chosen amount, and the expected output should be the token and minimum quantity you intended to receive.
A preview may not fully capture what happens if market conditions change before execution, and it does not remove smart-contract, liquidity, token, or network risk. A transfer-tax token, a paused token contract, insufficient gas, or a restrictive token rule can still cause an unexpected result or a failed transaction. A failed swap may also consume network fees, depending on how far execution progressed.
| What you see | What to do |
|---|---|
| The symbol is right but the address is unfamiliar | Stop and independently verify the contract address. |
| The approval is unlimited | Decide whether repeated use justifies the ongoing permission; otherwise use a bounded amount. |
| The quoted output changed after approval | Review the refreshed minimum received amount and reassess the trade. |
| The simulation shows an extra token movement | Do not sign until you can explain every asset movement. |
Reduce the exposure left behind after the swap
After the transaction confirms, verify it in your wallet or a block explorer by checking the input amount, output token address, received amount, and transaction status. If the output token does not display, confirm that it is on the correct network and that its contract address is the one you expected before adding it to the wallet view.
Finally, review any remaining allowance. A bounded approval may be partly unused; an unlimited approval may remain in place indefinitely. For assets you no longer plan to trade, revoke or reduce the allowance through a method you trust, accounting for the network fee required to change it. Make that allowance review part of the final check before moving on to the next trade.