Most common errors
Transaction errors
When sending or swapping TON, tokens, or NFTs, the following errors may occur:
- 'Insufficient funds'
- 'Failed to calculate fee'
- 'Something went wrong'
- 'An error occurred'
These issues most commonly happen for two reasons:
Not enough TON or Battery charges to cover the network fee.
To complete a transaction, you need:
- 0.1 TON (~10 Battery charges) for sending TON or other tokens. For HMSTR, you need 0.2 TON (~30 charges).
- 0.3 TON (~50 Battery charges) for swapping TON or tokens. For HMSTR, you need 0.5 TON (~120 charges).
- 0.1 TON (~4 charges) for sending NFTs.
If you don't have enough TON, you can always purchase Battery charges to proceed.
- Using an outdated version of Tonkeeper.
- Older versions of the app may not work correctly.
Check for updates in the App Store or Google Play to make sure you have the latest version installed.
Swap error: 'Failed. Increase the slippage tolerance in the swap settings to avoid this error.'
This error occurs when the token price changes between creating the transaction request and executing it. For example, the token price might have unexpectedly increased or decreased.
To resolve this:
- Increase the Slippage Tolerance.
- Tap 'Swap,' then click the settings icon in the top left corner and adjust the slippage percentage as needed.
Error 'Emulation error: no response; status code: undefined'
An emulation error may be encountered when confirming a transaction from the external app/website (e.g., a mini app in Telegram). This occurs due to insufficient TON to cover the network fee. Top up your wallet balance and try again.
Error 'Access Denied'
If you encounter an error while confirming a transaction using your PIN code or Face/Touch ID, it may be due to an interruption in the confirmation process (like closing the PIN input window by clicking the "X"). Please attempt to confirm the transaction again.
Error 'BitString Overflow'
You attempted a transaction with a message that is too long. Please reduce the number of characters in the 'Comment' field to avoid this error in the future.