I keep getting "Gas estimate failed" on a pancakeswap testnet for my new token.

Any idea what is causing this?

Could my token logic be too complex so it cant estimate gas, meaning it cant trade?

I really need help with this. I have absolutely no idea why its failing.

This may be a problem with the node. Try to change the rpc

Im using metamask with the Binance Smart Chain testnet? What other RPC's are there?

BSC RPC Endpoints:
• https://data-seed-prebsc-1-s1.binance.org:8545/
• https://data-seed-prebsc-2-s1.binance.org:8545/
• https://data-seed-prebsc-1-s2.binance.org:8545/
• https://data-seed-prebsc-2-s2.binance.org:8545/
• https://data-seed-prebsc-1-s3.binance.org:8545/
• https://data-seed-prebsc-2-s3.binance.org:8545/

I tried a few of these and im getting the exact same problem .

Its a new contract that i have never tried on pancakeswap before.

Could i be doing something in the contract that is breaking pancakeswap?

The contract successfully works on Address to Address transfers.

Im currently using https://pancake.kiemtienonline360.com/#/swap for testing pancakeswap functionality on the bsc testnet. Are there any others i can use?

Ok. Try setting a custom gasLimit. For example: await contract.testFunc({gasLimit: 500000})

Is that something i put into my contract?

No. Into front-end. Where called pancake func.

I cant modify that. Its pancakeswap, i cant cant control their UI.

It has something to do with my transfer method. I simplified it and it started working. I guess im doing too much and metamask cant figure out how much gas to estimate.

basic math?

Do you not know how to transfer funds from code?

What do the number of runs do when optimizing code?

Typically you would set the number of runs to be about as many times you expect the code to be executed. Higher runs can mean smaller gas usage for transactions, at the downside of larger bytecode (higher deployment gas usage).

So when you are ready to deploy to the main net you would set this to 10's of millions in the hope that the token is successful?

You usually set this to 999999 for maximum optimization.

no, a number that high would be overkill and really only increase your deployment cost...most people do a few hundred or a few thousand

Does metamask have a problem estimating gas for the transfer method which calls a bunch of nested methods? When I make my transfer method too complex I have problems with Pancakeswap interacting with metamask with a error estimating gas.