Honeypot code needs updating

[Gcvanasel]

Take a recently added contract as an example: 0xe4B473c657120ebc91586c335ad9E5aF203F2dC3
Look at the transfer and approve functions.

I see more complex code poping up to bypass honeypot identification bots.

Let me know if you would like to collab in finding a way to be optimal in finding the 1% of tokens that are not scams

[BytePhoenixCoding]

Yeah I totally get what u mean, it isn't very sophisticated at all it just looks for the most common code used for honeypots. I haven't tested how many honeypots can bypass the bot but I know it wouldn't be hard (they've prob looked at my code lol).

I find bscheck.eu to be quite good at spotting scam coins although I have no idea how it manages to detect honeypots. I think it will do a better job than the bot anyway.

The number 1 problem with the bot is it can't detect rug pulls. When tokens are given liquidity it isn't usually locked until a bit later, unless you could get the bot to quickly sell after buying then losing ur money is less likely.

But I'd be happy to work with you, whats your socials?

[Gcvanasel]

I think the only way to prevent hard rugs are to front run their transactions and to do that you need to run your own node. I don't ape in unless there is a minimum of 10BNB liquidity. Then monitor the transactions and as soon as liquidity is being removed up the gas limit and price and attempt to front run the rug.

Drop me a line on Telegram: CvA_CryptoPlayground

My time zone is GMT+2

[BytePhoenixCoding]

Nice mate thank you, will dm you tomorrow

[Gcvanasel]

Enhancement not an issue