-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NO TRADING PAIR, but Market Buy SUCCESS (not really) ? #27
Comments
- Bug from: BinaryDevil/binance-pump-bot#27 - Removes created invalid pair orders (which is not real order) Signed-off-by: IceWinterBot506 <[email protected]>
@0ldF0x check the modified bot I made here: https://github.com/Frost-Binance-Pump-Bot/The-Bot I already fixes the bugs, buy market with 100% and added some few touches |
Great, thanks! Will definitely check it out! |
@IceWinterBot506
|
The problem is that your balance is small to sell or buy. Common problem if using btc pair. I suggest you do some pre run using blank wallet. Also the percent changes from binance node api is kinda weird because of the triple or even quadro decimals of percent (eg. 1.592% or sometimes 0.9224%) the reason why hard take profit is triggering because of the weird decimal percent changes. It causes to sell the coin you got even on the small decimal percent changes. I already sent this to the dev of binance api node about weird decimal percent printings. Besides try to use the latest changes I made, and do some blank wallet run (change your wallet pair to BNB or BUSD). |
Hello!
I've used this great script in the launch of some new coin (let's name it "newcoin") on the binance.
I've entered coin exactly at launch and I got this log (see at bottom).
Any idea why buy purchase of coin didn't succeed ?
First warning was "WARN: NO TRADING PAIR", but then script continued with the messages "Market Buy 11% SUCCESS", but actually it didn't buy anything.
I probably started script few seconds too fast. But shouldn't script automatically stop on "NO TRADING PAIR" message?
The text was updated successfully, but these errors were encountered: