Author

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

sr. member
Activity: 252
Merit: 250
legendary
Activity: 1050
Merit: 1000
Mine the hottest new coins at ipoMiner.com
URGENT ANNOUNCEMENT TO ALL BUYERS

Long version:
Lately, we have been receiving complaints that hashing rate on Ipominer is only several percents of what NiceHash reports. Today, we have been contacted by Ipominer and took a deeper look into the situation. We found out, that there was an issue with difficulty, where Ipominer pool sent lower diff before sending higher diff, but then using lower diff to calculate hashing speed. That resulted in very poor performance shown on Ipominer.

Now, we are not fully sure, what kind of software Ipominer use for stratum, but if it is something publicly available, it means that there may be other pools with same issue.

We have applied temporary fix for this situation and Ipominer is now again compatible with NiceHash.

If you detect such issue in future, please, do not hesitate to contact us, but also provide details. Claiming only that you get bad hashrate does not help us analyse the issue.

In short: NiceHash did not cheat anyone. There is a bug in stratum software used by Ipominer (and perhaps some other pools).

I'm glad to see that NiceHash finally addressed this issue at our insistence, after days on end of customer complaints. Seeing as how I'm the one that brought the issue of their failure to respect difficulty settings properly to their attention, I find their blaming of ipoMiner to be extremely disingenuous.

Let's review their claim here that ipoMiner was erroneously sending lower difficulty before sending higher difficulty with a bit more detail...

1) Sgminer, and every other mining software released to date, have always worked perfectly with ipoMiner's stratums, and show correct behavior in their console. Here's a recent example from my own sgminer I ran as a test today:

Code:
[14:03:00] Probing for an alive pool
[14:03:00] Pool 0 difficulty changed to 1.573
[14:03:00] Pool 0 difficulty changed to 0.016
[14:03:01] Network diff set to 1.2K
[14:03:05] Accepted 1fe58d97 Diff 0.031/0.016 GPU 1 at Pool 0

As you can see, difficulty is initially set to 1.573 and then changed to 0.016, which is the configured difficulty for that worker.

2) These issues with NiceHash began approximately 7-10 days ago, and have been ongoing since then. Users have complained about this, but they have done nothing to address the issue until now. In addition to seeing problems with NiceHash at ipoMiner, I've also heard several other large, popular pools having similar problems with NiceHash usage as well recently.

Now, during that time period, NiceHash has been under DDoS attacks and recently moved to a new proxy server, which we initially assumed were the likely causes of their problems. However, after digging into it more in the past 24 hours, I realized that the real issue is that they were not respecting difficulty retargeting properly.

3) To disprove their claim that we erroneously were sending lower difficulty before sending higher difficulty, let's look at a tcpdump of a single connection from a miner at our proxy layer:

Code:
{"id": 0, "method": "mining.subscribe", "params": ["sgminer/4.1.0"]}
{"error": null, "id": 0, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "f8004373", 4]}
{"params": [1.572864], "id": null, "method": "mining.set_difficulty"}
{"id": 1, "method": "mining.authorize", "params": ["Wuher.1", "x"]}
{"params": [0.016384], "id": null, "method": "mining.set_difficulty"}

This is for an X11 miner connection, and as you can see, just like in the sgminer console output, a difficulty of 1.572864 (equivalent to scrypt difficulty of 49152) is initially set, then the configured worker difficulty of 0.016384 is set.
sr. member
Activity: 280
Merit: 250
URGENT ANNOUNCEMENT TO ALL BUYERS

Long version:
Lately, we have been receiving complaints that hashing rate on Ipominer is only several percents of what NiceHash reports. Today, we have been contacted by Ipominer and took a deeper look into the situation. We found out, that there was an issue with difficulty, where Ipominer pool sent lower diff before sending higher diff, but then using lower diff to calculate hashing speed. That resulted in very poor performance shown on Ipominer.

Now, we are not fully sure, what kind of software Ipominer use for stratum, but if it is something publicly available, it means that there may be other pools with same issue.

We have applied temporary fix for this situation and Ipominer is now again compatible with NiceHash.

If you detect such issue in future, please, do not hesitate to contact us, but also provide details. Claiming only that you get bad hashrate does not help us analyse the issue.

In short: NiceHash did not cheat anyone. There is a bug in stratum software used by Ipominer (and perhaps some other pools).
sr. member
Activity: 280
Merit: 250
I couldn't find any references - what is it about at all? Keep in mind, we do not offer mining of Darkcoin, we only offer shares being validated (x11) and forwarded on and that is being done with help of stratum protocol. We don't use Darkcoin wallets.

http://wiki.darkcoin.eu/wiki/Important

We don't run Darkocode wallet. We are just running stratum proxy that forwards work of miners to the remote pools.
legendary
Activity: 1946
Merit: 1100
Leading Crypto Sports Betting & Casino Platform
I couldn't find any references - what is it about at all? Keep in mind, we do not offer mining of Darkcoin, we only offer shares being validated (x11) and forwarded on and that is being done with help of stratum protocol. We don't use Darkcoin wallets.

http://wiki.darkcoin.eu/wiki/Important
sr. member
Activity: 280
Merit: 250
Since the last update the service is more stable but there are still connection problems, sometimes the miner has to restart the connection sometimes not, I get lot's of following messages:

stratum_recv_line failed
Stratum connection interrupted

This happens when our stratum terminates connection to your rig. Make sure you are not sending too many rejects.
member
Activity: 130
Merit: 10
Since the last update the service is more stable but there are still connection problems, sometimes the miner has to restart the connection sometimes not, I get lot's of following messages:

stratum_recv_line failed
Stratum connection interrupted
newbie
Activity: 14
Merit: 0
Will fresh algo be in nicehash soon?
newbie
Activity: 23
Merit: 0
How is the Payout for Nicehash compared to a decent sized ordinary multipool like trademybit.com??
Unless there are massive amount of buyer to compete with each other on the bids, the price should always be noticeably lower than a decent sized traditional multipool, given their profit switching are both efficient.

Good question. I moved to trademybit yesterday when nicehash had its problems. I must be misunderstanding something here so can some check my numbers?

Nicehash    X13 paying 0.5 BTC/day/Ghash this is 0.0005 BTC/day/Mhash (1GHash = 0.001Mhash)
TradeMyBit X13 paying 0.00079 BTC/day/Mhash which is 0.79 BTC/day/Ghash (currently via APEX, but I autoexchange to BTC)

So doesn't that make TradeMyBit more profitable? 0.79 vs 0.5?
Assuming the stats are both inaccurate, then I would say my actual BTC payments are much higher with TMB?
Is this because I have just a very small minnow running around 10Mhash/s?

Interested in the views of others

sr. member
Activity: 260
Merit: 250
How is the Payout for Nicehash compared to a decent sized ordinary multipool like trademybit.com??
Unless there are massive amount of buyer to compete with each other on the bids, the price should always be noticeably lower than a decent sized traditional multipool, given their profit switching are both efficient.
sr. member
Activity: 401
Merit: 250
Just released a new version of NiceHash Control.  Now has features to prevent flickering between algorithms if two are paying close to the same amount.

sr. member
Activity: 560
Merit: 250
sr. member
Activity: 280
Merit: 250
front page says x13 most profitable but miners mining x15
 Angry
A significant lack of information in that post... How is your miner configured?  Did you specify custom multi-algo factors?

my miner was working good till now
here is my pools

Code:
	{
      "name" : "NiceHash_X11",
      "url" : "stratum+tcp://stratum.nicehash.com:4336",
      "user" : "1KYPapEzhxvpLwb6eZB1DBg9joq2hVsz55",
      "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
      "profile": "x11"
    },
    {
      "name" : "NiceHash_X13",
      "url" : "stratum+tcp://stratum.nicehash.com:4337",
      "user" : "1KYPapEzhxvpLwb6eZB1DBg9joq2hVsz55",
      "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
      "profile": "x13"
    },
    {
       "name" : "NIST5_multi",
          "url" : "stratum+tcp://stratum.nicehash.com:4340",
          "user" : "1KYPapEzhxvpLwb6eZB1DBg9joq2hVsz55",
          "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
          "profile": "nist"
     },
{
      "name" : "NiceHash_X15",
      "url" : "stratum+tcp://stratum.nicehash.com:4339",
      "user" : "1KYPapEzhxvpLwb6eZB1DBg9joq2hVsz55",
      "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
      "profile": "x15"
    },

now nciehash miningx13 but my miners mining x15

We have updated default factors several days ago. Check here what kind of default factors we use: https://www.nicehash.com/multialgo/
sr. member
Activity: 560
Merit: 250
front page says x13 most profitable but miners mining x15
 Angry
A significant lack of information in that post... How is your miner configured?  Did you specify custom multi-algo factors?

my miner was working good till now
here is my pools

Code:
	{
      "name" : "NiceHash_X11",
      "url" : "stratum+tcp://stratum.nicehash.com:4336",
      "user" : "1KYPapEzhxvpLwb6eZB1DBg9joq2hVsz55",
      "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
      "profile": "x11"
    },
    {
      "name" : "NiceHash_X13",
      "url" : "stratum+tcp://stratum.nicehash.com:4337",
      "user" : "1KYPapEzhxvpLwb6eZB1DBg9joq2hVsz55",
      "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
      "profile": "x13"
    },
    {
       "name" : "NIST5_multi",
          "url" : "stratum+tcp://stratum.nicehash.com:4340",
          "user" : "1KYPapEzhxvpLwb6eZB1DBg9joq2hVsz55",
          "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
          "profile": "nist"
     },
{
      "name" : "NiceHash_X15",
      "url" : "stratum+tcp://stratum.nicehash.com:4339",
      "user" : "1KYPapEzhxvpLwb6eZB1DBg9joq2hVsz55",
      "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
      "profile": "x15"
    },

now nciehash miningx13 but my miners mining x15
newbie
Activity: 3
Merit: 0
Everything seems ok now <3
hero member
Activity: 700
Merit: 500
front page says x13 most profitable but miners mining x15
 Angry
A significant lack of information in that post... How is your miner configured?  Did you specify custom multi-algo factors?
sr. member
Activity: 560
Merit: 250
front page says x13 most profitable but miners mining x15
 Angry
sr. member
Activity: 280
Merit: 250
We did some software upgrade now. Try it out.
newbie
Activity: 23
Merit: 0
Guys, keep in mind, we are under DDOS attack still. The protection is doing mostly a good job, filtering most of shit out, but here and there, it may happen that you get filtered out too.

Its a shame you are under DDOS attack but a 'protection' system that takes us out as well isn't so great.
There is so little profit to be had these days that dropping out unpredictably for hours isn't much use.
eg; dropping out for 2 hours in 24 means a 8% loss

Can you let us know when you think its sorted, and I will switch back?

Thanks
sr. member
Activity: 280
Merit: 250
Guys, keep in mind, we are under DDOS attack still. The protection is doing mostly a good job, filtering most of shit out, but here and there, it may happen that you get filtered out too.
Jump to: