bonesoul / CoiniumServ

Next-gen crypto currency mining pool software
Other
797 stars 494 forks source link

Coinium & Nicehash #693

Open Caberhagen opened 10 years ago

Caberhagen commented 10 years ago

Hi @ all

i make a test with nicehash, the pool verificator shows all ok. but it wan't connect. On Worker Pages it shows a worker without address.

Have anyone the solution?

Bilder-Upload.eu - share DEINE Bilder

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5696298-coinium-nicehash?utm_campaign=plugin&utm_content=tracker%2F401667&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F401667&utm_medium=issues&utm_source=github).
frndxyz commented 10 years ago

i have same problem i did it yesterday..

frndxyz commented 10 years ago

but there is one more client connected to my VTC pool and mining well. i dont know what's the problem..

Caberhagen commented 10 years ago

I have tried on scrypt and sha 256. The same result for both. Pool verificator is on both ok. But wan't connect. Am 03.11.2014 13:23 schrieb "frndxyz" notifications@github.com:

but there is one more client connected to my VTC pool and mining well. i dont know what's the problem..

— Reply to this email directly or view it on GitHub https://github.com/CoiniumServ/CoiniumServ/issues/693#issuecomment-61470540 .

ghost commented 10 years ago

The Problem is that CoiniumServ uses different stratum protocol than most pools.. you have to use a stratrum proxy which logs this..

nicehash sends {"id":0,"method":"mining.subscribe","params":["NiceHash/1.0.0"]}

and waits for answer in the form ( trademybit.com ) {"id":0,"result":[[["mining.set_difficulty","deadbeefcafebabe0600000000000000"],["mining.notify","deadbeefcafebabe0600000000000000"]],"28000005",4],"error":null}

but CoiniumServ sends {"jsonrpc":"2.0","result":[["mining.set_difficulty","0","mining.notify","0"],"70000003",4],"id":0}

so nicehash gets a timeout

the syntax is okay, but there is no "error":null tag!

i wrote a proxy which fixes that.. so it runs very well with nicehash!

hint: for 1 ghash set very high diff like 262144 and no vardiff! with vardiff, you get very much rejected shares as nicehash sends obviously "old" shares with the wrong diff

bonesoul commented 10 years ago

will be fixing this within (https://github.com/int6/hpool-stratum/issues/1)

frndxyz commented 9 years ago

can you send me proxy for pool @buechling

ghost commented 9 years ago

no.. i am sorry, but it is part of a complex multipool software.. i use it for a private pool.. maybe the pool will be public soon..

frndxyz commented 9 years ago

@raistlinthewiz can you fix this issue quickly in c# version. many of nicehash client are try to use my pool but not able to connect and going with bad impression..

agentsmith5443 commented 9 years ago

Okay same bug here.

"will be fixing this within (int6/hpool-stratum#1)"

vkynchev commented 7 years ago

@bonesoul @agentsmith5443 @frndxyz @buechling @Caberhagen For anyone interested in the solution... It was in the JsonRpc package. I've downloaded, changed the source and compiled the package again. Now "error": null is showing if there is no error...

Link to commit