Qubit algorithm for connectivity with NH

ip019
Archived posts: 11
Joined: Sep 30, 2019

Re: Qubit algorithm for connectivity with NH

by ip019 · · Post #25061

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}
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Qubit algorithm for connectivity with NH

by Steve Sokolowski · · Post #25062

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.
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Qubit algorithm for connectivity with NH

by Steve Sokolowski · · Post #25064

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!
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Qubit algorithm for connectivity with NH

by Steve Sokolowski · · Post #25072

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
Archived posts: 11
Joined: Sep 30, 2019

Re: Qubit algorithm for connectivity with NH

by ip019 · · Post #25073

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 Fri Oct 04, 2019 03:44 PM UTC by ip019; edited 2 time(s).
ip019
Archived posts: 11
Joined: Sep 30, 2019

Re: Qubit algorithm for connectivity with NH

by ip019 · · Post #25074

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 Fri Oct 04, 2019 03:42 PM UTC by ip019; edited 1 time(s).
ip019
Archived posts: 11
Joined: Sep 30, 2019

Re: Qubit algorithm for connectivity with NH

by ip019 · · Post #25075

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
}