This usually happens when trading tokens with low liquidity.

That means there isn't enough of one of the tokens you're trying to swap in the Liquidity Pool: it's probably a small-cap token that few people are trading.

However, there's also the chance that you're trying to trade a scam token which cannot be sold. In this case, Kalichainisn't able to block a token or return funds.

The error is caused by trying to add or remove liquidity for a liquidity pool (LP) with an insufficient amount of token A or token B (one of the tokens in the pair).

It might be the case that prices are updating too fast when and your slippage tolerance is too low.

OK, so you're really determined to fix this. We really don't recommend doing this unless you know what you're doing.

There currently isn't a simple way to solve this issue from the Kalichainwebsite: you'll need to interact with the contract directly. You can add liquidity directly via the Router contract, while setting amountAMin to a small amount, then withdrawing all liquidity.

Approve the LP contract

Head to the contract of the LP token you're trying to approve.

For KALIS, here's the ETH/WBNB pair:

https://bscscan.com/address/0x70d8929d04b60af4fb9b58713ebcf18765ade422

1. Select Write Contract, then Connect to Web3 and connect your wallet.

2. In section "1. approve", approve the LP token for the router by entering

1. spender (address): enter the contract address of the LP token you're trying to interact with

2. value (uint256): -1

Query "balanceOf"

1. Switch to Read Contract.

2. In 5. balanceOf, input your wallet address and hit Query.

3. Keep track of the number that's exported. It shows your balance within the LP in the uint256 format, which you'll need in the next step.

Add or Remove Liquidity

Head to the router contract:

https://bscscan.com/address/0x05ff2b0db69458a0750badebc4f9e13add608c7f#writeContract

1. Select Write Contract and Connect to Web3 as above.

2. Find addLiquidity or removeLiquidity (whichever one you're trying to do)

3. Enter the token addresses of both of the tokens in the LP.

4. In liquidity (uint256), enter the uint256 number which you got from "balanceOf" above.

5. Set a low amountAMin or amountBMin: try 1 for both.

6. Add your wallet address in to (address).

7. Deadline must be an epoch time greater than the time the tx is executed.

This can cause very high slippage, and can cause the user to lose some funds if frontrun

This issue is caused by tokens which have hard-coded the V1 Kalichainrouter into their contract.

While this practice is ill-advised at best, the reason for these projects having done this appears to be due to their tokenomics, in which each purchase sends a % of the token to LPs.

The projects affected will likely not work with the V2 router: they will most likely need to create new versions of their tokens pointing to our new router address, and migrate any existing token holders to their new token. We recommend that any projects which created such tokens should also make efforts to prevent their users from adding them to V2 LP.

The up-to-date router address is https://bscscan.com/address/0x10ED43C718714eb63d5aA57B78B54704E256024E

This usually happens when trading tokens with insufficient slippage allowance on Trust Wallet.

The exact details of the problem are still being investigated.

This error happens when trading tokens with insufficient allowance, or when a wallet has insufficient funds.

If you're trading tokens with Restorative Rebase like tau assets tDoge or tBTC, make sure you understand how they work first with this guide to Rebase tokens.

If that still fails, you can perform an “emergency Withdraw” from the contract directly to unstake your staked tokens.

1. Go to: https://bscscan.com/address/0x73feaa1eE314F8c655E354234017bE2193C9E24E#writeContract

2. Click "Connect to Web3" and connect your wallet

3. In section "4. emergency Withdraw", enter "0" and click "Write".

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

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

To stop this happening again, don’t sell your SYRUP. You still need it to unstake from the “Stake KALIS Earn KALIS” pool.

This error has happened because you have sold or transferred SYRUP tokens. SYRUP is minted in a 1:1 ratio to KALIS when you stake in the KALIS-KALIS Syrup Pool. SYRUP must be burned at a 1:1 ratio to KALIS when calling leaveStaking (unstaking your KALIS from the pool), so if you don't have enough, you can't unstake from the pool.

Tenderly Dashboard

Tenderly is an Ethereum monitoring, debugging and analytics platform. It empowers blockchain teams and individuals by providing a powerful Debugger, intuitive Gas Profiler, Transaction Simulations, Monitoring and Alerting capabilities, Advanced Analytics and so much more.

Basically, your wallet (Metamask, Trust Wallet, etc.) can't finish what it's trying to do.

Your wallet estimates that the gas limit is too low, so the function call runs out of gas before the function call is finished.

This happens when you set a limit on your spend allowance when you first approved the contract, then try to swap more than the limit.

This happens when you set a limit on your spend allowance when you first approved the contract, then try to swap more than the limit.