Bot hangs at Waiting for next round #9
Replies: 19 comments 4 replies
-
|
Hi, thanks for reporting. Why was the Binance API url giving you an error? How long did you wait after the round started? usually after the round opens, you have to wait 1 minute before you see anything displayed. |
Beta Was this translation helpful? Give feedback.
-
|
Binance API was saying bad response from server on bot launch. I'm in the US if that matters, found the other URL via a google search. Oh yeah, I've waited way more than one minute. I've ran as my user, ran as root. Let it run for a few hours last night, still just sat at waiting for the next round no matter how long. Waiting time in the config is still 265000 |
Beta Was this translation helpful? Give feedback.
-
|
I tried changing the binance url. I managed to start the bot correctly, with the default settings, except the simulated mode. Seems to work fine, try to see if the smart contract listeners are being invoked correctly. |
Beta Was this translation helpful? Give feedback.
-
|
To see if smart contract listeners are working. Try inserting console logs and relaunch the bot. I expect the message to be printed. Inside the pcs-bot.js file under EVENTS.START_ROUND_EVENT put a console.log. I made you a screenshot of how to do it. console.log('START_ROUND_EVENT IS TRIGGHERED!');
|
Beta Was this translation helpful? Give feedback.
-
|
Added that code and relaunched. It still just sits and sits on Waiting for next round. I don't see any additional log files, and nothing is printing on the screen that wasn't before. Where do you reference BSC_NODE_PROVIDER_URL? I'm wondering since I'm in the US and had issues hitting api.binance.com, but data.binance.com works fine for the price calls, I wonder if perhaps the BSC node isn't passing the traffic it should for the script? |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, I'll check it out when I get home from work. Have you tried checking that the abi and url of the smart contract are correct? |
Beta Was this translation helpful? Give feedback.
-
|
@lloydwoods Noticed you said you were using the release. I haven't tried the release, but am having mostly success with cloning the repository. @lmusarella has done a fantastic job fixing a couple of issues that I have reported recently, but I'm not sure if the release version has been updated to reflect those changes. You might try just cloning the repo. Btw, thanks for pointing out about how to fix the Binance API errors. I am also getting those errors, so I will try changing the URL. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately I can't reproduce your case, however Try re-downloading the project from scratch. I used https://www.quicknode.com/ to define my node on the BSC chain.
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah. I don't know either. I'm a Linux novice, but I think everything is in order. It didn't like the newest version of openjs originally, but I managed to install 14.16 which it was happy with. I cloned again and still no dice. I was asking where in the code that BSC_NODE_PROVIDER_URL is defined? Like I found the constant files for the binance price, but I'm not seeing where BSC_NODE_PROVIDER_URL is defined in the code of this script, I was going to try some other URLs for it. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same issue as @lloydwoods has, it;s stuck at waiting for next round BSC_NODE_PROVIDER_URL = https://bsc-dataseed1.binance.org |
Beta Was this translation helpful? Give feedback.
-
Yeah, I know what node URLs to use, but the script itself calls BSC_NODE_PROVIDER_URL, what other files is that particular constant defined in so I can try a different URL to see if that's my issue? If I knew where in the script that BSC_NODE_PROVIDER_URL is actually defined by the URL I can edit that and try a different node. |
Beta Was this translation helpful? Give feedback.
-
|
You mean these? I think you really only need to edit the .env file. I'm using QuickNode and it doesn't hang on the first round.
|
Beta Was this translation helpful? Give feedback.
-
|
To modify the variable: BSC_NODE_PROVIDER_URL you need to open the ".env" file. I recommend using an editor or IDE like VisualStudio. My node version is 17.1.0 I finally managed to replicate your problem. it is surely the fault of the URL of the node that you have chosen. I copied "https://bsc-dataseed1.binance.org/" in my BSC_NODE_PROVIDER_URL property and here is the result. The same problem.
We can see that round 156964 has already started but I didn't get any hits on the console. Your same problem.
I advise you to use https://www.quicknode.com/ and set up your own node. It's completely free and easy to stetup. |
Beta Was this translation helpful? Give feedback.
-
|
Nice! |
Beta Was this translation helpful? Give feedback.
-
|
@rootisareservedword OMG, I didn't even thing about it being in the env file.....that was the issue. |
Beta Was this translation helpful? Give feedback.
-
|
@lmusarella You were correct, I built my own node and put that in and it's working perfectly now. Shoot me your BSC address, this is worthy of a little tip. |
Beta Was this translation helpful? Give feedback.
-
|
Is it difficult to build your own BSC node? I had a private node in the past but was paying someone monthly to use it. And how goes the signal strategy? Does it bet every round? |
Beta Was this translation helpful? Give feedback.
-
hello, there are free services that allow you to create your own node on the BSC chain. For example Quick node, maybe try to see some tutorial on how to do it. To answer the second question, the signals strategy executes the bet only in case the percentage (configured threshold) is satisfied. In case you use the martingale, instead the bot executes the bets in a linear way, i.e. it doesn't bet until the last bet is finished. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome~ thank you very much my friend! I was able to create a free one thru Quick Node! I do have a suggestion - as I am using the martingale strategy and have figured out that if you increment the bet amount by 2.7, you will get ahead in profit even with lower odd wins. So my strategy is doing the minimal bet amount of 0.001 BNB and then multiplying this by 2.7 with every loss. My stop loss is currently 0.62 BNB, which totals to 7 consecutive losing bets using 2.7 as the multiplier. However, the bet configurations are currently in USD and because BNB is always changing value, sometimes my minimum bet amount of 0.001 BNB, which is currently 0.31 USD, can fall below the threshold of the minimum bet amount. Are you able to put the bet configurations in BNB? For example, BET_AMOUNT, DAILY_GOAL and STOP_LOSS in BNB instead of USD. This would greatly improve it! You're doing a great job~ this is an awesome piece of software! |
Beta Was this translation helpful? Give feedback.
-
|
Perfect, thank goodness! 0x0C40e4F3606aE2F41DAc9bB67606f41284755350 This is my wallet, thank you for reporting it. |
Beta Was this translation helpful? Give feedback.
-
|
Wow, the solution is here, I was having the same problem. This bot has a perfect finish and it very complete. Looking forward to do some botting without the problem. |
Beta Was this translation helpful? Give feedback.
-
|
I made the quicknode and the problem does still seem to occur sometimes. Something to redundantly check the round and continue the betting process would be amazing. I think that people with not the best internet connection will run into this problem more often. |
Beta Was this translation helpful? Give feedback.
-
|
The code / contract interaction still seems to bug with the rounds, resulting in getting stuck. *It's simulation mode, maybe this works fine in normal mode... |
Beta Was this translation helpful? Give feedback.
-
Just found your release and thought I would give it a whirl. I can launch it via yarn or npm, neither give me errors (oh, BTW, I did have to change the API constants from api.binance.com to data.binance.com as I was getting an error on that) but the bot runs and just sits eternally on "Waiting for next round: XXXXXX". It displays the correct upcoming round number, and will change if I close the script and re-launch it, but it never progresses past this point.
It is not writing anything to the logs, which I find interesting.
Beta Was this translation helpful? Give feedback.
All reactions