Avoiding Common Transaction Issues

Motion is designed for seamless trading, but certain issues can occasionally prevent transactions from processing correctly. Understanding the most common problems and how to resolve them can help ensure smooth trading.

Insufficient MOVE for Fees

Every transaction on the Movement Network requires MOVE to cover gas fees. If a wallet does not have enough MOVE, transactions will fail.

Solution:

• Check the wallet balance before executing a trade or withdrawal.

• Deposit additional MOVE if needed to cover fees.

Slippage Errors

If a trade fails to execute, it may be due to slippage settings being too low. This happens when the market moves too quickly, and the price changes before the order is processed.

Solution:

• Increase slippage in the settings menu.

• For high-volatility trades, setting slippage to 100% may be necessary.

Pending Transactions

A transaction may get stuck in a pending state due to network congestion or a low gas fee.

Solution:

• Check the transaction status on a blockchain explorer.

• If a transaction remains pending for an extended period, try resubmitting it with adjusted settings.

Unable to Sell a Token

If a sell transaction fails, it could be due to restrictions placed by the token deployer. Some common reasons include:

• The token has anti-sell mechanics or trading limits, such as freeze capabilities.

• The token team has removed liquidity, making it impossible to sell.

Solution:

• Verify the token’s smart contract details to check for any restrictions.

• If the token appears to be a scam or honeypot, it may not be sellable.

Incorrect Wallet Selection

If a user cannot find their token balance, it may be due to the wrong wallet being selected.

Solution:

• Open the wallet management section and confirm that the correct wallet is active.

• If multiple wallets are being used, ensure the transaction was executed from the correct one.

Invalid Withdrawal Address

If a withdrawal fails, it may be because the recipient address is incorrect or does not support the token being sent.

Solution:

• Double-check the withdrawal address before confirming the transaction.

• Ensure the receiving platform supports the token being withdrawn.