Troubleshooting Errors

Sometimes you may find yourself facing a problem that doesn't have a clear solution. These troubleshooting tips may help you solve problems you run into.

Issues on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

The transaction cannot succeed due to error: EGSwapRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an issue with one of the tokens you are swapping.

The transaction cannot succeed due to error: execution reverted:EGSwapRouter: insufficient_output_amount.

You're trying to swap tokens, but your slippage tolerance is too low or liquidity is too low.

  • Refresh your page and try again later.

  • Try trading a smaller amount at one time.

  • Increase your slippage tolerance:

    1. Tap the settings icon on the liquidity page.

    2. Increase your slippage tolerance a little and try again.

  • Lastly, try inputting an amount with fewer decimal places.


INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

Fail with error 'EGSwapRouter: INSUFFICIENT_A_AMOUNT' or Fail with error 'EGSwapRouter: INSUFFICIENT_B_AMOUNT'

You're trying to add/remove liquidity from a liquidity pool (LP), but there isn't enough of one of the two tokens in the pair.

Refresh your page and try again, or try again later.

Still doesn't work?

  1. Tap the settings icon on the liquidity page.

  2. Increase your slippage tolerance a little and try again.


EgSwapRouter: EXPIRED

The transaction cannot succeed due to error: EGSwapRouter: EXPIRED. This is probably an issue with one of the tokens you are swapping.

Try again, but confirm (sign and broadcast) the transaction as soon as you generate it.

This happened because you started making a transaction, but you didn't sign and broadcast it until it was past the deadline. That means you didn't hit "Confirm" quickly enough.


EGSwap: K

The transaction cannot succeed due to error: EGSwap: K. This is probably an issue with one of the tokens you are swapping.

Try modifying the amount on “To” field. Therefore putting "(estimated)" symbol on “From”. Then initiate the swap immediately.

This usually happen when you are trying to swap a token with its own fee.


EGSwap: TRANSFER_FAILED

The transaction cannot succeed due to error: execution reverted: EGSwap: TRANSFER_FAILED.

Make sure you have 30% more tokens in your wallet than you intend to trade, or try to trade a lower amount. If you want to sell the maximum possible, try 70% or 69% instead of 100%. Caused by the design of Restorative Rebase tokens like tDoge or tBTC. Understand how restorative rebase tokens work.

Another possible cause of this issue is the malicious token issuer suspended trading for their token or they made selling action only possible for selected wallet addresses. If the token you are trying to swap failed with this error code is coming from an airdrop, that is most likely a scam. Please do not perform any token approval or follow any links, your fund may be at risk if you try to do so. Always do your own research to avoid any potential fraud.


Transaction cannot succeed

Try trading a smaller amount, or increase slippage tolerance via the settings icon and try again. This is caused by low liquidity.


Price Impact too High

Try trading a smaller amount, or increase slippage tolerance via the settings icon and try again. This is caused by low liquidity.


Cannot read property 'toHexString' of undefined

"Unknown error: "Cannot read property 'toHexString' of undefined"

When trying to swap tokens, the transaction fails and this error message is displayed. This error has been reported on mobile devices using Trust Wallet.

  • Attempt the transaction again with increased slippage allowance.

  • If 1. does not resolve your problem, consider using another wallet such as SafePal for your transaction.


Execution reverted: TransferHelper: TRANSFER_FROM_FAILED.

The transaction cannot TREATS due to error: execution reverted: TransferHelper: TRANSFER_FROM_FAILED.

When trying to swap tokens, the transaction fails and this error message is displayed. This error has been reported across platforms.

  • Check to make sure you have sufficient funds available.

  • Ensure you have given the contract allowance to spend the amount of funds you're attempting to trade with.


Issues with EGSwap Pools

Out of Gas error

Warning! Error encountered during contract execution [out of gas]

You have set a low gas limit when trying to make a transaction.

Try manually increasing the gas limit (not gas price!) in your wallet before signing the transaction.

A limit of 200000 is usually enough.

The above example is from Metamask; check your wallet's documentation if you aren't sure how to adjust the gas limit.


BEP20: transfer amount exceeds allowance

Fail with error 'BEP20: transfer amount exceeds allowance'

  • Use Unrekt.net to revoke approval for the smart contract you're trying to interact with

  • Approve the contract again, without setting a limit on spend allowance

  • Try interacting with the contract again.


BEP20: transfer amount exceeds balance

Fail with error 'BEP20: transfer amount exceeds balance'

You're probably trying to unstake from an EGSwap Pool with low rewards in it. Solution below.

If not, you may be trying to send tokens that you don't have in your wallet (for example, trying to send a token that is already assigned to a pending transaction). In this case, just make sure you have the tokens you're trying to use.

Firstly, let the team know which pool you're trying to unstake from, so they can top up the rewards. If you're in a hurry to unstake and you don't mind losing your pending yield, try an emergencyWithdraw:

You can perform an “emergencyWithdraw” from the contract directly to unstake your staked tokens.

  1. Find the contract address of the EG Pool you're trying to unstake from. You can find it in your wallet's transaction log.

  2. Go to https://bscscan.com/ and in the search bar, enter the contract address.

  3. Select Write Contract.

  4. In section “4. emergencyWithdraw”, enter "0" and click “Write”.

This will unstake your staked tokens and lose any uncollected yield.

This will lose any yield that you haven’t harvested yet.


Other issues

Provider Error

Provider Error No provider was found

This happens when you try to connect via a browser extension like MetaMask or Binance Chain Wallet, but you haven’t installed the extension.

Install the official browser extension to connect, or read our guide on how to connect a wallet to EGSwap


Unsupported Chain ID

Switch your chain to Binance Smart Chain. Check your wallet's documentation for a guide if you need help.


Buying $EG and similar tokens

This transaction will not succeed either due to price movement or fee on transfer. Try increasing your slippage tolerance.

To trade EG and similar tokens (whose taxes may vary), you must click on the settings icon and set your slippage tolerance accordingly (to 5% or more for EG).

This is because EGSwap taxes a 5% fee on each buy/sell transaction:

This is also why you might not receive as much of the token as you expect when you purchase.


Internal JSON-RPC errors

"MetaMask - RPC Error: Internal JSON-RPC error. estimateGas failed removeLiquidityETHWithPermitSupportingFeeOnTransferTokens estimateGas failed removeLiquidityETHWithPermit "

Happens when trying to remove liquidity on some tokens via Metamask. The root cause is still unknown. Try using an alternative wallet.

Internal JSON-RPC error. { "code": -32000, "message": "insufficient funds for transfer" } - Please try again.

You don't have enough BNB to pay for the transaction fees. You need more BEP-20 network BNB in your wallet.


Error: [ethjs-query]

Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32000,"message":"transaction underpriced"}}}"

Increase the gas limit for the transaction in your wallet. Check your wallet's documentation to learn how to increase gas limit.

Swap failed: Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32603,"message":"handle request error"}}}'

Cause unclear. Try these steps before trying again:

  1. Increase gas limit

  2. Increase slippage

  3. Clear cache

Last updated