To use the appendWorkerNames features, just turn on the "appendWorkerNames" parameters of your pool in the configuration file:
{
"name" : "Nicehash X11",
"host" : "stratum.nicehash.com:3336",
"user" : "19wv8FQKv3NkwTdzBCQn1AGsb9ghqBPWXi",
"password" : "d=0.02;p=0.24",
"enableExtranonceSubscribe" : true,
"appendWorkerNames" : true,
"workerNameSeparator" : ".",
"useWorkerPassword" : false,
"isEnabled": true
}
With the above example, your miners will be authorizes the names: 19wv8FQKv3NkwTdzBCQn1AGsb9ghqBPWXi.<miner1Name>, 19wv8FQKv3NkwTdzBCQn1AGsb9ghqBPWXi.<miner2Name>...
The miner1Name and miner2Name are names that are configured in your mining software to connect to the proxy. So if in your miner, you were using 19wv8FQKv3NkwTdzBCQn1AGsb9ghqBPWXi.miner1 before using the proxy, you now have to use only miner1.
You can change the workerNameSeparator if the pool uses another separator than '.' between the first part and the second part of the name (for Nicehash/Wafflepool, between the BTC address and the worker name). The "useWorkerPassword" has to be turned on only if you want to authorize the workers with their own password instead of the one configured for the pool in the proxy.
If you are using Nicehash with its new WorkerName feature, I have not done test. There may be some issues since the appendWorkerNames was implemented for MPOS based pools. I see one potential issue. If there is no worker which connect on the proxy for a while, no authorization are sent to Nicehash (but subscribe request is sent). Maybe Nicehash has a timeout between the subscribe request and the authoriation request. So your proxy will be often disconnected from Nicehash.
Moreover, I am not sure that Nicehash accept several workers by connection (maybe, maybe not).
Thanks for the great work!
I would also like to know how to get different workers to work on Nice hash. The reason why is this. I have 3 miners. 1 Is a Gridseed black which is 25 M/hs second which works great at around 4096 difficulty. And 2 Gridseed blades with a total of 4 cards each at 2.5 M/hs for a total of 10 M/hs. When I connect to other pools(say wafflepool) I split the workers into 5 workers so I can optimize the speeds of the card. Ie. I'll connect the black at d=4096 and the 4 other cards as d=256 or d=512. Here would be my username config:
bitcoinaddress.black -p d=4096(or 2048 depending on the pool)
Connection syntax on miner GUI dialog box: bitcoinaddress.black
bitcoinaddress.blade1 -p d=256(or 512)
bitcoinaddress.blade2 -p d=256(or 512)
bitcoinaddress.blade3 -p d=256(or 512)
bitcoinaddress.blade4 -p d=256(or 512)
Connection syntax on miner GUI dialog box: bitcoinaddress.blade1, bitcoinaddress.blade2, bitcoinaddress.blade3, bitcoinaddress.blade4
The problem is is since I can't assign different workers to different speeds Nice hash counts up ALL the workers for a total of around 30-35 M/hs to determine difficulty. No matter even if I put in my config file "d=4096" as a compromise for the difficulty level. After a while around say 45 minutes or so(sometimes longer) the proxy server is slowly climbing in difficulty until it hits around 8196 or even 16384 before the hashrate goes to nothing and the proxy server goes "haywire" then the difficulty starts back down to what was pre-set or say 512(when I use just a generic "x" password) and then slowly climbs up again to to 8196 or 16384 then goes "haywire" again then reconnects. As such my hashrate has suffered. Even when it is "working" at 4096 or 8196 it's way too high a difficulty for the blades as even if I comprimise the blades into one worker (10 M/hs) which only slightly less optimized and does work at say 2048 or even 1024 difficulty. What I would like to do is have a minimum of 2 workers on different difficulty settings if possible make it optimized with 5 ideally. Is there anyway the workers can connect to the proxy server and the proxy server handles different difficulty settings per different workers?
My basic config file:
{
"isScrypt" : true,
"disableStratum" : true,
"pools" :
[
{
"name" : "Nicehash Scrypt",
"host" : "stratum.nicehash.com:3333",
"user" : "<bitcoinaddress>.black",
"password" : "x",
"enableExtranonceSubscribe" : true
},
{
"name" : "Westhash Scrypt",
"host" : "stratum.westhash.com:3333",
"user" : "<bitcointalk>.black",
"password" : "x",
"enableExtranonceSubscribe" : true
}
]
}
For fun I tried this:
"name" : "Nicehash Scrypt",
"host" : "stratum.nicehash.com:3333",
"user" : "<bitcoinaddress>.black, <bitcoinaddress>.blades",
"password" : "d=4096, d=1024",
"enableExtranonceSubscribe" : true
Obviously no go.
I'm assuming it might look like this:
{
"name" : "Nicehash scrypt",
"host" : "stratum.nicehash.com:3336",
"user" : "<mybitcoinaddress>",
"password" : "x", <--- Do I delete this so that it uses the worker passwords?
"enableExtranonceSubscribe" : true,
"appendWorkerNames" : true,
"workerNameSeparator" : ".",
"useWorkerPassword" : true,
"isEnabled": true
}
Then I use the GUI syntax I normally use for say wafflepool:
bitcoinaddress.black -p d=4096(or 2048 depending on the pool)
Connection syntax on miner GUI dialog box: bitcoinaddress.black
bitcoinaddress.blade1 -p d=256(or 512)
bitcoinaddress.blade2 -p d=256(or 512)
bitcoinaddress.blade3 -p d=256(or 512)
bitcoinaddress.blade4 -p d=256(or 512)
would that be correct? Except I'm assuming you don't need to have the bitcoin address as the username. Ie I could use:
blade1, blade2, blade3, blade4 because the proxy server is connecting under my bitcoin address already correct?
Hell even if I can "lock" the difficulty at say 4096 or 2048 that would be fine but it always changes no matter what which I'm assuming is a nice hash deal. I'm assuming it's fighting with the boxes with the blades saying "easier, easier" and the black saying "harder, harder". I can tell when it's going to puke as it will go up to 8196 difficulty or higher with a shitload of rejects and within 10 minutes it will crap out and go back down to 512 or default or whatever. I'm asuming it's going up to 8196 because it starts mining a crazy easy coin. Howerver nicehash never tells you what coin it's mining otherwise I would have pool difficulty metrics for you to troubleshoot. What I think is happening is it mines a crazy easy coin at 8196 for a while then changes to a harder coin but still stays at the superhigh difficulty so nicehash probably is fooled into thinking it's disconnected from that miner and cuts it off. Then the proxy reconnects and Nice hash treats it as a new connection and starts the difficulty at 512 again slowly climbing up. If I could either A "lock" the difficulty or B put my boxes on different difficulty levels it would stabilize it greatly.
Just noticed now when the proxy server goes "haywire" it's switching from 128 difficulty up to 32K and back again trying to get some shares in. Restarting the proxy server fixes it. I hope that helps.
