Author

Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 341. (Read 794443 times)

member
Activity: 61
Merit: 10
cgminer 3.7.2 has many many bugs that have since been patched in newer versions and branches such as sgminer.  There's really no good reason to be using an old version of cgminer anymore - switch to sgminer.

-snip-
sgminer lacks GridSeed support, i'm more familiar with the cgminer codebase, sgminer dropped SHA suppport and baked in lots of code that makes it difficult to patch in new algorithms, i get better performance from cgminer 3.7.2 with Kalroth's tweaks, sgminer was susceptible to the client.reconnect exploit last time i checked (fixed by this commit in the latest build), R. M. Davidson's patches don't apply to sgminer out of the box, and my build would be a headache to break into pieces to migrate to sgminer + latest cgminer + misc cgminer forks for other algos. "switch to sgminer" may be a fine solution for many, but not for me today. Wink

The bug we're talking about it related to correct handling of extra nonce 2 (extranonce2, xnonce2) size. In cgminer 2.7.2 xnonce is fixed to 4 ... however by stratum protocol this should be "dynamic/resizable". Well, actually you should ask ckolivas for details regarding that ... I'm not sure in which exact version this was patched but if you can find out I'll be very glad if you'd share the info here.
thanks! i'll drop a patch here when i track down the issue and get around to testing fixes.

Well, what we're seeing here with this cgminer-3.7.2 is similar to WinXP story ... to many users of too old software, and when support ends it's "Houston, we've got problems" Wink

-snip-
similar in the sense that a large part of the userbase didn't like the new direction and chose to rebel against it, but this is free software. cgminer 3.7.2 is still actively improved upon, though unfortunately there's a distinct lack of collaboration among devs, (myself included. Roll Eyes)
legendary
Activity: 2296
Merit: 1031
Hi, I recently joined.  Looks like it mined for a while but then went to all zeroes after first payment?  My bfgminer shows like it is still connected and trying to work but no accepted shares. 17vNQiv5zTQ7sAhKMqmCiZzYg1FWozDG4x

Maybee your miner wasn't able to reconnect after a connection failure ... make sure you have properly configured backup pools, stable internet connection, etc. ... PM if you have some other issues.

Never had that issue on any other pool and there were a lot of other miners at zero.  Please answer back when you have a better idea.
sr. member
Activity: 457
Merit: 273
Dear users, thanks for bringing us at 1+ GH/s! We'll introduce a small fee in the next days. NiceHash will charge a processing fee from each party of hash rate trade made through the service. Our fee is as low as 2%. In the future the amount of the fee will vary based on a 30 day volume with discounts for the fee to be as low as 0.5% (we'll introduce fee schedule later). Thanks again and wish you all Nice hashing!
sr. member
Activity: 457
Merit: 273
Hi, I recently joined.  Looks like it mined for a while but then went to all zeroes after first payment?  My bfgminer shows like it is still connected and trying to work but no accepted shares. 17vNQiv5zTQ7sAhKMqmCiZzYg1FWozDG4x

Maybee your miner wasn't able to reconnect after a connection failure ... make sure you have properly configured backup pools, stable internet connection, etc. ... PM if you have some other issues.
legendary
Activity: 2296
Merit: 1031
Hi, I recently joined.  Looks like it mined for a while but then went to all zeroes after first payment?  My bfgminer shows like it is still connected and trying to work but no accepted shares. 17vNQiv5zTQ7sAhKMqmCiZzYg1FWozDG4x

I will try a restart of my miner but this issue needs fixed...

Thanks
sr. member
Activity: 457
Merit: 273
Yeah, we're aware of it. This is also what phzi was talking about a couple of posts back. The issue is with the stratum protocol, which currently doesn't support changing the extranonce1. Therefore currently the only option is to disconnect a rig in reconnect it to new order. We'll see if we'll find a technical solution for this.
It's possible to fix =).  Multi-pools have had this issue in the past.

Hmm, stratum protocol actually doesn't support changing extranonce1 without disconnect, so I'd be very glad if you know how multi-pools solved this. And than again, NiceHash doesn't operate as a multi-pool behind the scenes, it's a quite different approach. But if you have some hint or a link please post it.
hero member
Activity: 700
Merit: 500
Yeah, we're aware of it. This is also what phzi was talking about a couple of posts back. The issue is with the stratum protocol, which currently doesn't support changing the extranonce1. Therefore currently the only option is to disconnect a rig in reconnect it to new order. We'll see if we'll find a technical solution for this.
It's possible to fix =).  Multi-pools have had this issue in the past.

However, another, organizational solution is already being implemented - will make sure orders don't switch too fast. There will be a minimum order time frame (not too long though, allowing for the buyers still to be flexible) and the possibility for order hash limit. This will allow more concurrent orders, less order switching and will make hash power providers to stay on single order for longer time. Will not be perfect, there will still be some disconnects form time to time. But at the end of the day we have to make some trade-offs between optimizations for sellers&buyers (we want to make a ~100% fair game for sellers&buyers). Stay tuned!
Sounds like a good plan.

---

I was just replying to your comment that everybody should switch from cgminer to sgminer - that's valid for GPUs only.

bfgminer has scaleability issues on Windows. Can't run more than a couple of instances, can't run more than ~20 miners. But that's another story, it's not a problem with nicehash.

I said everyone should stop using outdated mining software, and gave an example in sgminer.  Yes, sgminer is opencl only.  bfgminer would be an appropriate solution for miners with other hardware.  I have no doubt that there are scalability issues on Windows... I also have no idea why anyone would run windows on a dedicated mining rig.  And if you're using gridseeds, then a Pi is probably a better host platform solution.


---

Looks like the stratum is completely offline right now? - my miners all just fell back to a failover pool.

Nicehash.com not loading now either.
member
Activity: 74
Merit: 10
thanks to your fast answer.

Take your time to find the best solution to buyer and seller.
sr. member
Activity: 457
Merit: 273
But if you can solve the only problem that's will be perfect Smiley
When your pool switch to job there is a disconnection with the stratum server, if you can remove this disconnection Smiley
During 5-20 secondes rigs don't mining in order to reconenct the stratum server.

Yeah, we're aware of it. This is also what phzi was talking about a couple of posts back. The issue is with the stratum protocol, which currently doesn't support changing the extranonce1. Therefore currently the only option is to disconnect a rig in reconnect it to new order. We'll see if we'll find a technical solution for this. However, another, organizational solution is already being implemented - will make sure orders don't switch too fast. There will be a minimum order time frame (not too long though, allowing for the buyers still to be flexible) and the possibility for order hash limit. This will allow more concurrent orders, less order switching and will make hash power providers to stay on single order for longer time. Will not be perfect, there will still be some disconnects form time to time. But at the end of the day we have to make some trade-offs between optimizations for sellers&buyers (we want to make a ~100% fair game for sellers&buyers). Stay tuned!
member
Activity: 74
Merit: 10
Hi,

Your pool/concept is very amazing.

I put all my miner on it (~10Mhs).

But if you can solve the only problem that's will be perfect Smiley
When your pool switch to job there is a disconnection with the stratum server, if you can remove this disconnection Smiley
During 5-20 secondes rigs don't mining in order to reconenct the stratum server.
sr. member
Activity: 457
Merit: 273
Just to clarify: sgminer for Gridseed will not happen:
https://github.com/veox/sgminer/issues/154

Huh, didn't realize that Wink That's quite sad. Not nice to be a GridSeed user these days, latest cgminer is not an option since it's declared as "non-scrypt" and sgminer is not an option since it's declared as "opencl-only" Sad That leaves only two options: encourage luke-jr to incorporate GridSeed support into latest BFGminer or fork cgminer-3.7.2+upstream patches with GridSeed support and create "gsgminer" Wink

p.s.: there are already NiceHash supported options for GridSeed users, see here: https://www.nicehash.com/index.jsp?p=faq#faqs0
legendary
Activity: 3654
Merit: 8909
https://bpip.org
Anyway, the correct path would be to adopt newer software. The absolute correct path would be for the GridSeed community to step together and build modular approach for GridSeed support in sgminer/bfgminer so that it would be easy for veox/luke-jr to include support for GridSeeds in upstream versions. Not sure how to accomplish that though, community/gridseed users should step together for this.

Just to clarify: sgminer for Gridseed will not happen:
https://github.com/veox/sgminer/issues/154
legendary
Activity: 3654
Merit: 8909
https://bpip.org
sgminer doesn't support Gridseed
You can use bfgminer on gridseeds.  At least bfgminer is actively maintained with scrypt support.

I was just replying to your comment that everybody should switch from cgminer to sgminer - that's valid for GPUs only.

bfgminer has scaleability issues on Windows. Can't run more than a couple of instances, can't run more than ~20 miners. But that's another story, it's not a problem with nicehash.
sr. member
Activity: 457
Merit: 273
can anyone (kenshirothefist: *poke*) summarize the problem with cgminer 3.7.2 and NiceHash's scrypt pool, point out the breaking commit (between cgminer 3.1.1 and 3.7.2) or the fix (in sgminer) relating to it?

btw, great job on this service so far! it's great to see some innovative new pool ideas this year Grin
cgminer 3.7.2 has many many bugs that have since been patched in newer versions and branches such as sgminer.  There's really no good reason to be using an old version of cgminer anymore - switch to sgminer.

sgminer doesn't support Gridseed

Well, what we're seeing here with this cgminer-3.7.2 is similar to WinXP story ... to many users of too old software, and when support ends it's "Houston, we've got problems" Wink

Anyway, the correct path would be to adopt newer software. The absolute correct path would be for the GridSeed community to step together and build modular approach for GridSeed support in sgminer/bfgminer so that it would be easy for veox/luke-jr to include support for GridSeeds in upstream versions. Not sure how to accomplish that though, community/gridseed users should step together for this.

See FAQ "Which miners are supported?" https://www.nicehash.com/index.jsp?p=faq#faqs0 (BFGMiner is supported)

And if you really want to use cgminer, cgminer-3.1.1 (this version doesn't yet introduce the xnonce2 bug) is also supported (https://github.com/gridseed), but I really don't recommend to use these old versions.
hero member
Activity: 700
Merit: 500
sgminer doesn't support Gridseed
You can use bfgminer on gridseeds.  At least bfgminer is actively maintained with scrypt support.
sr. member
Activity: 457
Merit: 273
can anyone (kenshirothefist: *poke*) summarize the problem with cgminer 3.7.2 and NiceHash's scrypt pool, point out the breaking commit (between cgminer 3.1.1 and 3.7.2) or the fix (in sgminer) relating to it?

The bug we're talking about it related to correct handling of extra nonce 2 (extranonce2, xnonce2) size. In cgminer 3.7.2 xnonce is fixed to 4 ... however by stratum protocol this should be "dynamic/resizable". Well, actually you should ask ckolivas for details regarding that ... I'm not sure in which exact version this was patched but if you can find out I'll be very glad if you'd share the info here.
legendary
Activity: 3654
Merit: 8909
https://bpip.org
can anyone (kenshirothefist: *poke*) summarize the problem with cgminer 3.7.2 and NiceHash's scrypt pool, point out the breaking commit (between cgminer 3.1.1 and 3.7.2) or the fix (in sgminer) relating to it?

btw, great job on this service so far! it's great to see some innovative new pool ideas this year Grin
cgminer 3.7.2 has many many bugs that have since been patched in newer versions and branches such as sgminer.  There's really no good reason to be using an old version of cgminer anymore - switch to sgminer.

sgminer doesn't support Gridseed
hero member
Activity: 700
Merit: 500
can anyone (kenshirothefist: *poke*) summarize the problem with cgminer 3.7.2 and NiceHash's scrypt pool, point out the breaking commit (between cgminer 3.1.1 and 3.7.2) or the fix (in sgminer) relating to it?

btw, great job on this service so far! it's great to see some innovative new pool ideas this year Grin
cgminer 3.7.2 has many many bugs that have since been patched in newer versions and branches such as sgminer.  There's really no good reason to be using an old version of cgminer anymore - switch to sgminer.

---

Everytime the pool switches jobs, it seems to disconnect all my miners briefly.  Lost mining time appears to be 1-5 seconds everytime, but any work that was performed immediately prior is lost as well.  And sometimes when there are a bunch of small jobs, or several new jobs are posted in short succession, this is a pretty significant loss of hashrate.  It's super obvious for me, because the R9 290 fans spin up slightly when the GPU isn't under load (noise change is very noticeable).  With NiceHash, I hear the rig in my living room drop for a a few seconds several times in a minute sometimes.

I see this regularly on my consoles:
Code:
[21:50:14] Stratum connection to NiceHash interrupted
[21:50:15] NiceHash difficulty changed to 512

Code:
[21:50:14] Stratum connection to NiceHash interrupted
[21:50:14] NiceHash stratum share submission failure
[21:50:15] NiceHash difficulty changed to 512
[21:50:19] Network diff set to 84.7M
[21:50:19] New block detected on network before pool notification
[21:50:19] NiceHash communication resumed, submitting work
[21:50:20] Rejected 01529678 Diff 49.5K/512 GPU 1 NiceHash (Job not found.)

Code:
[22:08:30] Stratum connection to NiceHash interrupted
[22:08:31] NiceHash stratum share submission failure
[22:08:31] NiceHash difficulty changed to 32
[22:08:32] NiceHash difficulty changed to 64
[22:08:32] Network diff set to 10.4M
[22:08:32] Stratum from NiceHash detected new block
[22:08:32] Stratum from NiceHash requested work restart
[22:08:36] NiceHash communication resumed, submitting work
[22:08:36] Rejected cf84d7c0 Diff 316/32 GPU 4 NiceHash (Job not found.)
Code:
[22:08:30] Stratum connection to NiceHash interrupted
[22:08:30] Lost 2 shares due to stratum disconnect on NiceHash
[22:08:31] NiceHash stratum share submission failure
[22:08:31] NiceHash difficulty changed to 32
[22:08:32] NiceHash difficulty changed to 64
[22:08:32] Network diff set to 10.4M
[22:08:32] Stratum from NiceHash detected new block
[22:08:32] Stratum from NiceHash requested work restart
[22:08:36] NiceHash communication resumed, submitting work
[22:08:36] Rejected 04c785be Diff 54/32 GPU 3 NiceHash (Job not found.)
[22:08:36] Rejected 06e87f69 Diff 37/32 GPU 0 NiceHash (Job not found.)
Code:
[22:08:30] Stratum connection to NiceHash interrupted
[22:08:30] Lost 1 shares due to stratum disconnect on NiceHash
[22:08:30] NiceHash stratum share submission failure
[22:08:31] NiceHash difficulty changed to 32
[22:08:32] NiceHash difficulty changed to 64
[22:08:32] Network diff set to 10.4M
[22:08:32] Stratum from NiceHash detected new block
[22:08:32] Stratum from NiceHash requested work restart
[22:08:35] NiceHash communication resumed, submitting work
[22:08:36] Rejected 02350f7d Diff 116/32 GPU 2 NiceHash (Job not found.)
[22:08:36] Rejected 07b180d4 Diff 33/32 GPU 4 NiceHash (Job not found.)

There's no reason for the stratum server to be disconnecting miners like this when switching jobs.  Please fix.

Also, the server has been dropping me to down to low-diff on reconnects sometimes, even thought I have p=5.0;d=512 set as my password.

---

Edit: just observed 3 connection drops within 20 seconds.
member
Activity: 61
Merit: 10
can anyone (kenshirothefist: *poke*) summarize the problem with cgminer 3.7.2 and NiceHash's scrypt pool, point out the breaking commit (between cgminer 3.1.1 and 3.7.2) or the fix (in sgminer) relating to it?

btw, great job on this service so far! it's great to see some innovative new pool ideas this year Grin
newbie
Activity: 26
Merit: 0
Man, this pool (or hashrate exchange) is amazing! Especially the part where you can set both your minimum prize and diff as just your password.
Also, Since the last update my reject rates dropped to 0.5% from 5-7% earlier, keep up the good work!
Jump to: