Why Did My STON.fi Transaction Fail?
Failed STON.fi transaction does not mean the protocol is broken. Causes include wallet issues, fees, market movement, token conditions or on chain execution. Diagnose first.
1. Identify the operation
Determine whether you were swapping, adding or removing liquidity, farming or interacting with a custom token.
2. Check your $GRAM balance
STON.fi transactions require $GRAM to cover TON network fees. Confirm that your wallet has sufficient $GRAM.
3. Review swap conditions
Check the quoted rate, price impact, minimum received and slippage tolerance. Price impact shows how a trade affects available liquidity, while slippage protects against price movement between quotation and execution. Large trades or volatile markets can push execution outside acceptable limits. Increasing slippage blindly may accept a worse price.
4. Verify token warnings
For unfamiliar tokens, verify the official contract address and review warnings. A familiar name or logo does not prove that a token is genuine. Check its source and liquidity.
5. Check the TON transaction
Find the transaction hash or explorer link and confirm whether it was broadcast. If it was, inspect the on-chain result to see whether it succeeded, failed, or was bounced. If no transaction exists, investigate the wallet, signing or connection stage instead.
6. Isolate the cause
Reconnect the wallet and where appropriate, test with another compatible TON wallet. This helps identify wallet-specific issues.
7. Retry only after diagnosis
Do not repeatedly submit the same transaction without understanding the failure. Correct the likely cause first.
For support, provide the wallet address, transaction hash, operation type, token pair, amount, time, error message, wallet used and screenshots. Never share a seed phrase or private key.
Document the cause before repeating the operation.
Identify → Check → Verify → Inspect → Correct → Retry.
#BTC Price Analysis#
Failed STON.fi transaction does not mean the protocol is broken. Causes include wallet issues, fees, market movement, token conditions or on chain execution. Diagnose first.
1. Identify the operation
Determine whether you were swapping, adding or removing liquidity, farming or interacting with a custom token.
2. Check your $GRAM balance
STON.fi transactions require $GRAM to cover TON network fees. Confirm that your wallet has sufficient $GRAM.
3. Review swap conditions
Check the quoted rate, price impact, minimum received and slippage tolerance. Price impact shows how a trade affects available liquidity, while slippage protects against price movement between quotation and execution. Large trades or volatile markets can push execution outside acceptable limits. Increasing slippage blindly may accept a worse price.
4. Verify token warnings
For unfamiliar tokens, verify the official contract address and review warnings. A familiar name or logo does not prove that a token is genuine. Check its source and liquidity.
5. Check the TON transaction
Find the transaction hash or explorer link and confirm whether it was broadcast. If it was, inspect the on-chain result to see whether it succeeded, failed, or was bounced. If no transaction exists, investigate the wallet, signing or connection stage instead.
6. Isolate the cause
Reconnect the wallet and where appropriate, test with another compatible TON wallet. This helps identify wallet-specific issues.
7. Retry only after diagnosis
Do not repeatedly submit the same transaction without understanding the failure. Correct the likely cause first.
For support, provide the wallet address, transaction hash, operation type, token pair, amount, time, error message, wallet used and screenshots. Never share a seed phrase or private key.
Document the cause before repeating the operation.
Identify → Check → Verify → Inspect → Correct → Retry.
#BTC Price Analysis#
