[ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool

[odie158]

When you make order:

Non-refundable 0.0005 BTC is taken to prevent order spam.
Refundable 2% is taken for the service.

and

0.0004 BTC is returned in case there was no work performed - accepted or rejected shares (dead pool, no miners, etc).

ok

[odie158]

How about a feature that if a live order goes dead more than twice it is automatically canceled. As it is a user can place as many orders as he wants, one at every price point, and then go to his pool and change the names of his workers from: x.1, x.2, x.3... to x.a, x.b, x.c... this would make the worker appear dead. the user can then activate the worker at the best price point (by changing the name back to x.1)having it come back to life and bump the other users. if anyone places a bid at a higher price than the clever user he can simply activate the worker above the person who tried to outbid him.
this is what I believe is happening on the script market with the user with all of the 5.00 ghs limits (or it's a bot)

[nicehashdev]

We are already doing some changes regarding that and features are already in testing phase. The 0.0005 order fee will be removed (only 0.0001 will stay to prevent order spam), instead miners will be paid for activities that reduce their performance (pools going dead and very rapid work changes).

[JHammer]

Why is NiceHash not paying what its stats claim its making?  

I mean look here this proves what I am saying and what I started experiencing here early this week:  https://bitcointalk.org/index.php?topic=514242.0


Stats say been Avg right at 1.9 per GH pretty much for the past week or so...

But I was making more like 1.7..  to 1.5

Before when I was mining here the past few weeks, I was making spot on what the Stats were reporting I should make..

I am trying here again but will leave fast if this is still occurring.

Sure.. Its just a little but.. But with the MAJOR declining profits we are making, I need 100% of what it says I will make..


Talking Script..

[nicehashdev]

We are aware of the issue and I just explained what will be the changes soon in my last post. Some of our buyers are putting real stress to the rigs with many disconnects and work changes. We will make payments to miners for these actions.

[kupan787]

Any chance the API can be updated to display stats for the multi-algorithm mining normalized values?

[JHammer]

I get so frustrated.  Every time I mine here now 20 to 30% of my hash fails over to my back up pool and I cant tell why?

This never use to happen several weeks ago..

There looks like there is more then enough buyers here right??  Meaning there are more buyers here than there are miners to satisfy the buyers..

Is that correct?

[Vanguard*]

Any1 else having issues with seeds not connecting to the scrypt url???

[guzzzi]

Problems with the X13_Multi Algo? Got this NIght "NiceHash_X13_multi not responding!" ? And it seems SGMiner is dead doing nothing.

[kenshirothefist]

Regarding disconnects: yesterday we had internet network connectivity issues with our stratum servers (unplanned maintenance at ISPs; BGP routing issues, etc.), that's why you may have noticed many disconnects and flips to backup pools. Thing are working smoothly now, sorry for the inconvenience and thanks for understanding.

Regarding sgminer_v5 issues: as you already know, sgminer_v5 is still in development, you should regularly check:
- new commits: https://github.com/sgminer-dev/sgminer/commits/v5_0
- resolved issues: https://github.com/sgminer-dev/sgminer/issues?milestone=5&page=1&state=closed
- open issues: https://github.com/sgminer-dev/sgminer/issues?milestone=5&page=1&state=open

Lot's of issues have been resolved yesterday, including errors when compiling kernels, segfaults, uptime timer, etc. If you're using sgminer_v5 and you're building from source I strongly advise you to build new version from git (git clone -b v5_0 https://github.com/sgminer-dev/sgminer.git). We'll try to provide you with windows binaries later today, but if anyone else is compiling windows binaries - your welcome to drop them here.

[guzzzi]

Lot's of issues have been resolved yesterday, including errors when compiling kernels, segfaults, uptime timer, etc. If you're using sgminer_v5 and you're building from source I strongly advise you to build new version from git (git clone -b v5_0 https://github.com/sgminer-dev/sgminer.git). We'll try to provide you with windows binaries later today, but if anyone else is compiling windows binaries - your welcome to drop them here.

Many Thanks for the Information. Waiting for the new SG Version for Windows.

[guzzzi]

The Options

-pool-gpu-threads
-pool-gpu-powertune

are not available for the upper Configuration for each Algo? If i set this my SGmine breaks down and close after start (Windows).

[kenshirothefist]

Many Thanks for the Information. Waiting for the new SG Version for Windows.

Elun windows build: https://www.dropbox.com/s/atc8w343t0gqsxv/sgminer_v5_0_06062014.zip

Our builds: https://www.nicehash.com/software/#sgminer

[brucen]

I'm not sure if it's a sgminer 5.0 issue or if it the version compiled by NiceHash. I can't get the X13 algorithm to run more than 5 minutes when using the 4337 multi-switching port. I ran more than 24-hours without a problem when using the 3337 port, but then I don't have the switching capability.

Initially I thought I was pushing my GPU too hard and reduced the pool settings. However, any setting that works easily on port 3337 will result in a GPU error, or GPU DEAD message in sgminer when using port 4337. The GPU will mine for 5 minutes without a problem, then suddenly the hastrate falls to 0.000M and only a hard reboot will get the GPU back on track. Any idea what is port related that causes the GPU to stop working?

[nicehashdev]

It cannot be port related, because processing logic is exactly the same. 4xxx ports will get switched on/off. I suggest you to direct this question to sgminer devs.

[brucen]

It most likely is related to the switching of algorithms. Everything in the pool settings is identical except for the port. I'm trying the latest release with the marucoin-modold kernel to see if it makes a difference.

[dhsc19]

I'm not sure if it's a sgminer 5.0 issue or if it the version compiled by NiceHash. I can't get the X13 algorithm to run more than 5 minutes when using the 4337 multi-switching port. I ran more than 24-hours without a problem when using the 3337 port, but then I don't have the switching capability.

Initially I thought I was pushing my GPU too hard and reduced the pool settings. However, any setting that works easily on port 3337 will result in a GPU error, or GPU DEAD message in sgminer when using port 4337. The GPU will mine for 5 minutes without a problem, then suddenly the hastrate falls to 0.000M and only a hard reboot will get the GPU back on track. Any idea what is port related that causes the GPU to stop working?

Are you overclocking?

[brucen]

No overclocking. I have tried reducing the memclock, gpu-engine, thread-concurrency, and intensity settings, but nothing seems to make a difference with the 4337 port. When using the 3337 port, I can run the GPU at the same max settings I'm using for the other algorithms.

It may be kernal related because I'm now testing the marucoin-modold kernel that was released with the latest build and the pool has been running on port 4337 for 30 minutes at max settings. The marucoin and marucoin-mod kernels cause the GPU to die within minutes of start up.

Edit: Nope, GPU went to 0.000M after 45 minutes. I'll try reducing the settings and see what happens since the marucoin-modold is the most successful so far.

[oktay50000]

im getting to many getwork failures is this normal

[nicehashdev]

im getting to many getwork failures is this normal

Getwork is not being used on NiceHash, only stratum protocol. Not sure what would be the reason for miner to report getwork failures. Do you use any other pools besides NiceHash?