xmr-node-proxy
xmr-node-proxy copied to clipboard
super-low hashrate reported to pool?
Hey guys, first and foremost : props to your work! It's very obvious that what you have accomplished here must have taken a lot of time and effort.
I'm using xmr-cpu-stak The hashrate on my testdevice is about 400h/s, which get correctly reported to the xmr-node-proxy Both pool.supportxmr.com and mine.xmrpool.net won't exceed 30-120 h/s in their reports though
xmr-cpu-stak local hashrate : 400h/s
xmr-node-proxy hashrate : 350h/s
mine.xmrpool.net hashrate: 120h/s
I have configured 2 seperate aws-micro instances and I'm experiencing this problem with both servers.
My Config looks like this :
{
"pools": [
{
"hostname": "pool.supportxmr.com",
"port": 7777,
"ssl": false,
"allowSelfSignedSSL": false,
"share": 80,
"username": "xxx",
"password": "proxy:[email protected]",
"keepAlive": true,
"coin": "xmr",
"default": false
},
{
"hostname": "mine.xmrpool.net",
"port": 7778,
"ssl": false,
"allowSelfSignedSSL": false,
"share": 20,
"username": "xxx",
"password": "proxy:[email protected]",
"keepAlive": true,
"coin": "xmr",
"default": true
}
],
"listeningPorts": [
{
"port": 8080,
"ssl": false,
"diff": 5000,
"coin": "xmr"
},
{
"port": 8443,
"ssl": true,
"diff": 5000,
"coin": "xmr"
},
{
"port": 3333,
"ssl": false,
"diff": 10000,
"coin": "xmr"
}
],
"bindAddress": "0.0.0.0",
"developerShare": 3,
"daemonAddress": "127.0.0.1:18081",
"coinSettings": {
"xmr":{
"minDiff": 5000,
"maxDiff": 300000,
"shareTargetTime": 15
}
}
}
Does anybody have a pointer an idea about what i'm doing wrong here?
- Philipp
It's not the proxy, i guess it's the pool itself and their way to calculate average, just wait 15 or 30 minutes and you will see your real KH/s
You are sending 80% of your hash's towards SupportXMR and 20% to XMRPool.