Qubit algorithm for connectivity with NH

Encounter a problem related to the pool or have a request for a feature? Post your issue here and we will help you out.
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.

Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.

We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
ip019
Posts: 11
Joined: Mon Sep 30, 2019 7:11 am

Re: Qubit algorithm for connectivity with NH

Post by ip019 » Thu Oct 03, 2019 12:23 am

Verification process from different NH regions:

root@ubuntu:~/nicehash/_pool_verificator$ ./pool_verify.sh USA

Success: false

Pool host prohashing.com resolved to IP 50.225.198.65
Connecting to Stratum proxy for region: USA
Selected mining algorithm: Qubit
Sending mining subscribe request
Sending login information
Mining subscribe request successfully completed
Received mining set target
Received mining set difficulty
Pool difficulty too low (provided=1, minimum=4)



root@ubuntu:~/nicehash/_pool_verificator$ ./pool_verify.sh EUROPE

Success: false

Pool host prohashing.com resolved to IP 50.225.198.65
Connecting to Stratum proxy for region: EUROPE
Selected mining algorithm: Qubit
Sending mining subscribe request
Sending login information
Mining subscribe request successfully completed
Received mining set target
Received mining set difficulty
Pool difficulty too low (provided=1, minimum=4)


Pool settings for this check's above are:
password="a=qubit"
username=ip019
stratumPort=3448
stratumHost=prohashing.com
miningAlgorithm=QUBIT




{"success":false,"logs":[{"timestamp":"2019-10-03T04:18:40.187Z","level":"INFO","poolVerificationMessage":"POOL_HOST_RESOLVED_TO_IP","params":{"HOST":"prohashing.com","IP":"50.225.198.65"},"message":"Pool host prohashing.com resolved to IP 50.225.198.65"},{"timestamp":"2019-10-03T04:18:40.189Z","level":"INFO","poolVerificationMessage":"CONNECTING_TO_STRATUM_PROXY_FOR_REGION","params":{"REGION":"EUROPE"},"message":"Connecting to Stratum proxy for region: EUROPE"},{"timestamp":"2019-10-03T04:18:40.268Z","level":"INFO","poolVerificationMessage":"SELECTED_MINING_ALGORITHM","params":{"MINING_ALGORITHM":"Qubit"},"message":"Selected mining algorithm: Qubit"},{"timestamp":"2019-10-03T04:18:40.268Z","level":"INFO","poolVerificationMessage":"SENDING_MINING_SUBSCRIBE_REQUEST","message":"Sending mining subscribe request"},{"timestamp":"2019-10-03T04:18:40.269Z","level":"INFO","poolVerificationMessage":"SENDING_LOGIN_INFORMATION","message":"Sending login information"},{"timestamp":"2019-10-03T04:18:40.351Z","level":"INFO","poolVerificationMessage":"MINING_SUBSCRIBE_REQUEST_SUCCESSFUL","message":"Mining subscribe request successfully completed"},{"timestamp":"2019-10-03T04:18:40.352Z","level":"INFO","poolVerificationMessage":"RECEIVED_MINING_SET_TARGET","message":"Received mining set target"},{"timestamp":"2019-10-03T04:18:40.352Z","level":"INFO","poolVerificationMessage":"RECEIVED_MINING_SET_DIFFICULTY","message":"Received mining set difficulty"},{"timestamp":"2019-10-03T04:18:40.428Z","level":"SEVERE","poolVerificationMessage":"POOL_DIFFICULTY_TOO_LOW","params":{"PROVIDED_DIFFICULTY":"1","MINIMUM_DIFFICULTY":"4"},"message":"Pool difficulty too low (provided=1, minimum=4)"}],"highestDifficulty":0.0,"difficultyCorrect":false}
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Qubit algorithm for connectivity with NH

Post by Steve Sokolowski » Thu Oct 03, 2019 8:43 am

We did some more research into this issue and have not been able to determine the cause of the problem. The URL is still unable to be contacted from the mining servers.

Chris needs to perform some additional research to rule out a network configuration issue that only affects that port. After that, we'll submit a support ticket to Nicehash. Hopefully, I'll be able to make another post here tomorrow morning with an update on this issue.
ip019
Posts: 11
Joined: Mon Sep 30, 2019 7:11 am

Re: Qubit algorithm for connectivity with NH

Post by ip019 » Thu Oct 03, 2019 9:03 am

Steve Sokolowski wrote: Thu Oct 03, 2019 8:43 am The URL is still unable to be contacted from the mining servers.
Can you try this URL?

https://api2.nicehash.com/main/api/v2/m ... lgorithms/
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Qubit algorithm for connectivity with NH

Post by Steve Sokolowski » Thu Oct 03, 2019 3:48 pm

I was successfully able to figure out this issue. It seems like the URL was cached in my browser, which is why I initially thought that this problem was specific to the mining servers.

What actually happened is that the URL appears to be inaccessible from all servers, even though their documentation links to it. I changed the mining server to use the URL suggested by ip019, and modified the field names.

The fixes will be available in the next release. Thanks for your help!
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Qubit algorithm for connectivity with NH

Post by Steve Sokolowski » Fri Oct 04, 2019 9:36 am

This release has been made and this issue has now been resolved.
ip019
Posts: 11
Joined: Mon Sep 30, 2019 7:11 am

Re: Qubit algorithm for connectivity with NH

Post by ip019 » Fri Oct 04, 2019 10:17 am

I have just created 14 new test orders.
Four started with normal difficulty=4, and the remaining 10 are in dead status due to low pool difficulty.

Image
https://pasteboard.co/IAqaYap.png
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Qubit algorithm for connectivity with NH

Post by Steve Sokolowski » Fri Oct 04, 2019 10:54 am

I can't reproduce this issue. As far as I can tell, the mining server correctly assigns the cloud mining difficulty when I connect to that port. In the case of Qubit, that's 4, and in the case of x16rv2, that's 8. Both are successfully assigned. The issue was also not reproducible in Dev.

I'm not sure how to proceed with troubleshooting this issue. Do you have any ideas?
ip019
Posts: 11
Joined: Mon Sep 30, 2019 7:11 am

Re: Qubit algorithm for connectivity with NH

Post by ip019 » Fri Oct 04, 2019 11:38 am

I have no ideas yet, but I have some information.
Pool verification from NH to prohashing.com:3448 returns different result check for EUROPE and USA markets.

Pool verification from NH qubit server for EUROPE market.
NH EUROPE server IP address: 35.233.15.36:
root@ubuntu:~/nicehash/_pool_verificator$ ./pool_verify.sh EUROPE

Success: true

Pool host prohashing.com resolved to IP 50.225.198.65
Connecting to Stratum proxy for region: EUROPE
Selected mining algorithm: Qubit
Sending mining subscribe request
Sending login information
Mining subscribe request successfully completed
Received mining set target
Received mining set difficulty
Pool difficulty is correct (provided=4, minimum=4)


Pool verification from NH qubit server for USA market
NH USA marker IP address: 35.233.244.152:
root@ubuntu:~/nicehash/_pool_verificator$./pool_verify.sh USA

Success: false

Pool host prohashing.com resolved to IP 50.225.198.65
Connecting to Stratum proxy for region: USA
Selected mining algorithm: Qubit
Sending mining subscribe request
Sending login information
Mining subscribe request successfully completed
Received mining set target
Received mining set difficulty
Pool difficulty too low (provided=1, minimum=4)


A successful pool check from the EUROPE market does not guarantee that the order's state will change to normal in this situation.
Last edited by ip019 on Fri Oct 04, 2019 11:44 am, edited 2 times in total.
ip019
Posts: 11
Joined: Mon Sep 30, 2019 7:11 am

Re: Qubit algorithm for connectivity with NH

Post by ip019 » Fri Oct 04, 2019 11:41 am

Here is raw data from NH pool_verificator

From USA market:


{
"success": false,
"logs": [
{
"timestamp": "2019-10-04T15:18:26.047Z",
"level": "INFO",
"poolVerificationMessage": "POOL_HOST_RESOLVED_TO_IP",
"params": {
"HOST": "prohashing.com",
"IP": "50.225.198.65"
},
"message": "Pool host prohashing.com resolved to IP 50.225.198.65"
},
{
"timestamp": "2019-10-04T15:18:26.187Z",
"level": "INFO",
"poolVerificationMessage": "CONNECTING_TO_STRATUM_PROXY_FOR_REGION",
"params": {
"REGION": "USA"
},
"message": "Connecting to Stratum proxy for region: USA"
},
{
"timestamp": "2019-10-04T15:18:26.529Z",
"level": "INFO",
"poolVerificationMessage": "SELECTED_MINING_ALGORITHM",
"params": {
"MINING_ALGORITHM": "Qubit"
},
"message": "Selected mining algorithm: Qubit"
},
{
"timestamp": "2019-10-04T15:18:26.529Z",
"level": "INFO",
"poolVerificationMessage": "SENDING_MINING_SUBSCRIBE_REQUEST",
"message": "Sending mining subscribe request"
},
{
"timestamp": "2019-10-04T15:18:26.530Z",
"level": "INFO",
"poolVerificationMessage": "SENDING_LOGIN_INFORMATION",
"message": "Sending login information"
},
{
"timestamp": "2019-10-04T15:18:26.738Z",
"level": "INFO",
"poolVerificationMessage": "MINING_SUBSCRIBE_REQUEST_SUCCESSFUL",
"message": "Mining subscribe request successfully completed"
},
{
"timestamp": "2019-10-04T15:18:26.739Z",
"level": "INFO",
"poolVerificationMessage": "RECEIVED_MINING_SET_TARGET",
"message": "Received mining set target"
},
{
"timestamp": "2019-10-04T15:18:26.739Z",
"level": "INFO",
"poolVerificationMessage": "RECEIVED_MINING_SET_DIFFICULTY",
"message": "Received mining set difficulty"
},
{
"timestamp": "2019-10-04T15:18:26.919Z",
"level": "SEVERE",
"poolVerificationMessage": "POOL_DIFFICULTY_TOO_LOW",
"params": {
"PROVIDED_DIFFICULTY": "1",
"MINIMUM_DIFFICULTY": "4"
},
"message": "Pool difficulty too low (provided=1, minimum=4)"
}
],
"highestDifficulty": 0,
"difficultyCorrect": false
}
Last edited by ip019 on Fri Oct 04, 2019 11:42 am, edited 1 time in total.
ip019
Posts: 11
Joined: Mon Sep 30, 2019 7:11 am

Re: Qubit algorithm for connectivity with NH

Post by ip019 » Fri Oct 04, 2019 11:42 am

From EUROPE market:

{
"success": true,
"logs": [
{
"timestamp": "2019-10-04T15:41:26.316Z",
"level": "INFO",
"poolVerificationMessage": "POOL_HOST_RESOLVED_TO_IP",
"params": {
"HOST": "prohashing.com",
"IP": "50.225.198.65"
},
"message": "Pool host prohashing.com resolved to IP 50.225.198.65"
},
{
"timestamp": "2019-10-04T15:41:26.317Z",
"level": "INFO",
"poolVerificationMessage": "CONNECTING_TO_STRATUM_PROXY_FOR_REGION",
"params": {
"REGION": "EUROPE"
},
"message": "Connecting to Stratum proxy for region: EUROPE"
},
{
"timestamp": "2019-10-04T15:41:26.396Z",
"level": "INFO",
"poolVerificationMessage": "SELECTED_MINING_ALGORITHM",
"params": {
"MINING_ALGORITHM": "Qubit"
},
"message": "Selected mining algorithm: Qubit"
},
{
"timestamp": "2019-10-04T15:41:26.396Z",
"level": "INFO",
"poolVerificationMessage": "SENDING_MINING_SUBSCRIBE_REQUEST",
"message": "Sending mining subscribe request"
},
{
"timestamp": "2019-10-04T15:41:26.397Z",
"level": "INFO",
"poolVerificationMessage": "SENDING_LOGIN_INFORMATION",
"message": "Sending login information"
},
{
"timestamp": "2019-10-04T15:41:26.479Z",
"level": "INFO",
"poolVerificationMessage": "MINING_SUBSCRIBE_REQUEST_SUCCESSFUL",
"message": "Mining subscribe request successfully completed"
},
{
"timestamp": "2019-10-04T15:41:26.479Z",
"level": "INFO",
"poolVerificationMessage": "RECEIVED_MINING_SET_TARGET",
"message": "Received mining set target"
},
{
"timestamp": "2019-10-04T15:41:26.479Z",
"level": "INFO",
"poolVerificationMessage": "RECEIVED_MINING_SET_DIFFICULTY",
"message": "Received mining set difficulty"
},
{
"timestamp": "2019-10-04T15:41:26.556Z",
"level": "INFO",
"poolVerificationMessage": "POOL_DIFFICULTY_CORRECT",
"params": {
"PROVIDED_DIFFICULTY": "4",
"MINIMUM_DIFFICULTY": "4"
},
"message": "Pool difficulty is correct (provided=4, minimum=4)"
}
],
"highestDifficulty": 4,
"highestDifficultyFormatted": "4",
"difficultyCorrect": true
}
Post Reply