My idea is: let's check the liquidity of the tokens before the purchase, is it locked or not? I saw many tokens without locked liquidity making huge profit but it can be just a factor and if it's locked perhaps a good idea to instruct the bot to dare to buy for more BNBs than the unlocked ones. On Tokensniffer I saw tokens where there was not any liquidity locked at all, but section was not on alert, because the page said "it's enough tokens were already burned" and it's considered a "safe token". This part what I don't get really why burning can be equivalent to the liquidity locking..?
And I saw some tokens with Locks but on Mudra what I found a "fake" locker page, because those tokens had locked liquidity on Mudra were usually dumped to 0 after a little time. It didn't matter it was locked for a year, it matters if it's on Mudra or not.
Is is hard to check the liqudity locking in Typescript with web3? Or the token burn ratio if it's equivalent to it for a token?
I hope this repo isn't abandoned totally.
My idea is: let's check the liquidity of the tokens before the purchase, is it locked or not? I saw many tokens without locked liquidity making huge profit but it can be just a factor and if it's locked perhaps a good idea to instruct the bot to dare to buy for more BNBs than the unlocked ones. On Tokensniffer I saw tokens where there was not any liquidity locked at all, but section was not on alert, because the page said "it's enough tokens were already burned" and it's considered a "safe token". This part what I don't get really why burning can be equivalent to the liquidity locking..?
And I saw some tokens with Locks but on Mudra what I found a "fake" locker page, because those tokens had locked liquidity on Mudra were usually dumped to 0 after a little time. It didn't matter it was locked for a year, it matters if it's on Mudra or not.
Is is hard to check the liqudity locking in Typescript with web3? Or the token burn ratio if it's equivalent to it for a token?