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

[nicehashdev]

PM me your email address you registered with and screenshot of your wallet transaction history.

[aadje93]

I'm also thinking its a little bit weird pool.

I have 2 7950 rigs which both report 14,66m avg since start. and a 780 which is hashing @ 4900

while the pool reports only 26mhash!!. The rigs should be putting out a 28mhash and then 4,5 or so from the 780. 99%+ accepted rates.....

I'm switching to another pool until someone can convice me this is right.

[kenshirothefist]

We have published new sgminer_v5 binaries (linux, windows), build today ... most notable updates:

- completely new configuration options with profiles (remember to replace any pool-xxx setting with only xxx), take your time and read thoroughly all the details here: https://github.com/sgminer-dev/sgminer/blob/v5_0/doc/configuration.md
- support for 14.6 drivers
- new x11 (darkcoin-mod) and x13 (marucoin-mod) kernels (make sure you delete your old .bin files before running new version!)
- optimized nist5 (talkcoin-mod) kernel
- numerous bugfixes, also related to algorithm switching

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

[aznboy84]

We have published new sgminer_v5 binaries (linux, windows), build today ... most notable updates:

- completely new configuration options with profiles (remember to replace any pool-xxx setting with only xxx), take your time and read thoroughly all the details here: https://github.com/sgminer-dev/sgminer/blob/v5_0/doc/configuration.md
- support for 14.6 drivers
- new x11 (darkcoin-mod) and x13 (marucoin-mod) kernels (make sure you delete your old .bin files before running new version!)
- optimized nist5 (talkcoin-mod) kernel
- numerous bugfixes, also related to algorithm switching

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

I could use a small guide if you have it ... downloaded and run sgminer.exe but it just exit immediately without any message

[Kay0r]

Ordered some X11 power, canceled my order due to high price, made another but it doesn't show as active neither in the homepage nor in my orders section.
The pool i've pointed the hashpower handled well my previous order, but right now the worker isn't active and 0.08206208 BTC vanished.

Here's a snip of the order table highlighting the vanished order

2014-06-22 21:48:38   Comment: Fee order #24431   -0.00177474   
2014-06-22 21:48:36   Comment: Payment order #24431   -0.08206208

Can you please take a look at it?

[nicehashdev]

You created scrypt order and it is dead at the moment.

[Kay0r]

You created scrypt order and it is dead at the moment.

Thanks, i was worried 'cause the order showed up later than i supposed

[nwfella]

Just checking out your web site and decided to create an account.  Will try to get a rig pointed here sometime this evening if I can.

[jstefanop]

Can you guys add a way to link payment address to our accounts, so we don't have to go in the worker section and scroll down to find our payment address each time!

[brucen]

Can you guys add a way to link payment address to our accounts, so we don't have to go in the worker section and scroll down to find our payment address each time!

No need for NiceHash to do that for you. Just save a bookmark in your browser the next time you are on your payment page. Then you can go directly to the payment page each time without scrolling though the payment list.

[StuffOfInterest]

One feature I'd like to see added is worker identification such as the "address.workerid" format used by some other pools.  I have miners running on a couple of machines and it is easier to look at the stats page to make sure everything is running instead of going to look at the other machine. 

[nwfella]

lol...boy I guess I just picked the wrong time to try out this pool's sha256 situation.  Talk about bad timing.  I'll give it another go this evening seeing as how it looks like everything is back up!

[kenshirothefist]

Information for buyers: Due to increased transaction dust, produced from mining directly into NiceHash deposit address, we can not allow this anymore. Many small incoming transactions are increasing online wallet load and also increasing outgoing transaction fees. We ask you to mine into your personal wallet and then transfer funds in your NiceHash online deposit address - it will be faster (we only require 2 confirmations) and cheaper at the end of the day. Unfortunately we will have to disable mining directly into NiceHash deposit address at the beginning of the next week. Many online exchanges and similar services have implemented this kind of restrictions in the past. Thanks for understanding and thanks for using NiceHash!

[StuffOfInterest]

Information for buyers: Due to increased transaction dust, produced from mining directly into NiceHash deposit address, we can not allow this anymore. Many small incoming transactions are increasing online wallet load and also increasing outgoing transaction fees. We ask you to mine into your personal wallet and then transfer funds in your NiceHash online deposit address - it will be faster (we only require 2 confirmations) and cheaper in the end of the day. Unfortunately we will have to disable mining directly into NiceHash deposit address at the beginning of the next week. Many online exchanges and similar services have implemented this kind of restrictions in the past. Thanks for understanding and thanks for using NiceHash!

Another feature worth considering, payment threshold.  Possibly as another password parameter such as "t=0.02" to transfer when balance reaches 0.02 BTC.  If multiple values come in then take the lowest value recorded since the last payment.

[chococat211]

Hi Nicehash dev, is there white list so I can avoid you ban me, I'm using slow internet but my rig so big (~600MB) that give me too many reject (~3% to 7%)

My wallet add is: 17BEAnCpVk88wg8Eszmbw8periW1ZXv9BG (in case u can add me in your white list).

Thank you.

[kenshirothefist]

We have published new sgminer_v5 binaries (linux, windows), build today (60 sec quit fix, high speed fan fix, etc.): https://www.nicehash.com/software/#sgminer

[PonyBoy]

Are some people being given priority?

I noticed this problem affecting both scrypt and x13, it may affect the other algos as well.

Here is the problem. I put up an order for hash power, even tho it is above the lowest priced order that is hashing it never starts, even If I increase the price alot it will never start. I noticed alot of people having the same problem. It appears that some people are getting priority to hash first which is really shitty.

[nicehashdev]

I see nothing wrong. Keep in mind following:
- Orders are filled from top to bottom; top orders are filled first. If a lot of new orders appear or a lot of new orders become alive, then the picture you have shown would appear and it takes some time for rigs to get reassigned. We don't reassign rigs constantly, because that would give very bad performance to rig owners; we rather do that in approx. 2 minute intervals (reassigning 100-200 rigs at a time).
- Some of our customers use API, custom pools and can therefore manipulate when order is alive (if their pool terminates connection, then order gets dead and is pushed down the list - you get impression as if that order didn't exists). When this order gets alive again, it will be somewhere in the middle of the list and with 0 miners, waiting to get filled with miners. We do permit this kind of behavior because providers are awarded for connections dropped by remote pools.

[brucen]

We have published new sgminer_v5 binaries (linux, windows), build today (60 sec quit fix, high speed fan fix, etc.): https://www.nicehash.com/software/#sgminer

With the win32 compiled version I'm getting the same bin compilation error on all algorithms.

Code:

[14:34:57] Started sgminer 4.2.1
[14:34:57] Loaded configuration file Multi-Algo.conf
[14:34:57] Probing for an alive pool
[14:34:58] NiceHash_Scrypt_multi difficulty changed to 128
[14:34:59] Startup GPU initialization... Using settings from pool NiceHash_Scrypt_multi.
[14:34:59] Building binary ckolivasHawaiigw256l4lg2tc30592nf10.bin
[14:35:08] Initialising kernel ckolivas.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[14:35:08] Initialising kernel ckolivas.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[14:35:08] Building binary ckolivasCedargw256l4lg2tc1920nf10.bin
[14:35:08] Error -11: Building Program (clBuildProgram)
[14:35:08] "C:\Users\Azza\AppData\Local\Temp\OCLEFFB.tmp.cl", line 792: warning: variable
          "ySIZE" was declared but never referenced
  	const uint ySIZE = (N[NFACTOR]/LOOKUP_GAP+(N[NFACTOR]%LOOKUP_GAP>0));
  	           ^

"C:\Users\Azza\AppData\Local\Temp\OCLEFFB.tmp.cl", line 844: error: work group
          size exceeds the maximum default value for the selected device
  __attribute__((reqd_work_group_size(WORKSIZE, 1, 1)))
                 ^

1 error detected in the compilation of "C:\Users\Azza\AppData\Local\Temp\OCLEFFB.tmp.cl".

Frontend phase failed compilation.

Edit: Did the NiceHash developers use the latest version that fixes the Error -11 Building Program bug that was reported on the github site?

[nwfella]

I would like to second the vote on setting up some sort of payment threshold.  Some of us are pretty small time players and it would be nice to have the option of selecting when I wish to cash out.

*BTW, did anybody else notice a hiccup in the sha256 pool this afternoon or is just me?