GridSeed users: here is a cgminer 3.7.2 linux build with support for GridSeed ASIC miners (Mini USB miner and G-Blade miner) with some extra bugfixes, performance patches and NiceHash.com compatibility: https://www.nicehash.com/software/cgminer-gc3355-nicehash-linux.zip
Build based on this jmordica GIT source code: https://github.com/jmordica/cgminer-gc3355
Try it and report if it works for you.
Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 320. (Read 794443 times)
May 09, 2014, 12:03:15 PM
May 09, 2014, 11:35:01 AM
At Betarigs the price can be whatever you want to make it, doesn't mean it'll get rented, or that you won't get asked for partial refund if your rig doesn't perform as advertised for the duration of the rental period.
You know what a smart move would be? Set up your rig for rental at Leaserig or Betarig and, in the meantime, have it pointed at Nicehash as pool2 so that it can make a steady income for you while you wait for it to be rented.
You know what a smart move would be? Set up your rig for rental at Leaserig or Betarig and, in the meantime, have it pointed at Nicehash as pool2 so that it can make a steady income for you while you wait for it to be rented.
May 09, 2014, 10:10:02 AM
Why is the price so low?
In betarigs it is 0.00454 Btc per mh/s.
In betarigs it is 0.00454 Btc per mh/s.
May 09, 2014, 04:27:50 AM
Confusing UI. Have a look at betarigs their interface is clear.
This assertion indicates a lack of understanding as to the difference between manual leasing services, such as Betarigs and Leaserig, whereby you assign your rig to be available at a price and wait for someone to choose to rent it.
Nicehash allows you to simply point your miners at their service, state a Bitcoinwallet payment address as the user name and then just let it run. You will earn a steady Bitcoin income at the stated rate all the while your miner is hashing to the nicehash pool.
May 09, 2014, 04:13:43 AM
Confusing UI. Have a look at betarigs their interface is clear.
We welcome all suggestions. How would you like it then?
May 08, 2014, 10:49:47 PM
Does anyone know?
When using multiple workers to point to NiceHash can you use the same BTC address as the username for all the workers or do you have to give each one a different BTC address?
When using multiple workers to point to NiceHash can you use the same BTC address as the username for all the workers or do you have to give each one a different BTC address?
Same BTC address for multiple workers works fine.
Great! Thank you for the reply!
May 08, 2014, 10:46:04 PM
Does anyone know?
When using multiple workers to point to NiceHash can you use the same BTC address as the username for all the workers or do you have to give each one a different BTC address?
When using multiple workers to point to NiceHash can you use the same BTC address as the username for all the workers or do you have to give each one a different BTC address?
Same BTC address for multiple workers works fine.
May 08, 2014, 10:15:14 PM
Does anyone know?
When using multiple workers to point to NiceHash can you use the same BTC address as the username for all the workers or do you have to give each one a different BTC address?
When using multiple workers to point to NiceHash can you use the same BTC address as the username for all the workers or do you have to give each one a different BTC address?
May 08, 2014, 09:42:27 PM
Confusing UI. Have a look at betarigs their interface is clear.
BetaRigs is based on a completely different kind of rental system then NiceHash. NiceHash lets you lease hashes; BetaRigs lets you lease rigs.I like NiceHash and I understand that it's another system as BR or LS, but the user interface is really confusing in the beginning. Not intuitive at all. But I don't mind, that might keep prices low ^^
May 08, 2014, 09:27:19 PM
Confusing UI. Have a look at betarigs their interface is clear.
BetaRigs is based on a completely different kind of rental system then NiceHash. NiceHash lets you lease hashes; BetaRigs lets you lease rigs. May 08, 2014, 08:24:19 PM
Confusing UI. Have a look at betarigs their interface is clear.
May 08, 2014, 08:20:11 PM
May 08, 2014, 04:04:19 PM
Do u have any plan to add X11 support?
May 08, 2014, 02:19:36 PM
Any news on x11 mining?
May 08, 2014, 01:59:53 PM
when will my hosted miners with gawminers be able to work at nicehash? since they use cgminer
Good news. GAW miners software engineering team notified us that they have updated their cgminer software with our patches. GAW miners hosted miners should now work fine with NiceHash. Please try to connect your miners to NiceHash and let us know if all is fine now.
yes things are working fine
May 08, 2014, 12:55:36 PM
when will my hosted miners with gawminers be able to work at nicehash? since they use cgminer
Good news. GAW miners software engineering team notified us that they have updated their cgminer software with our patches. GAW miners hosted miners should now work fine with NiceHash. Please try to connect your miners to NiceHash and let us know if all is fine now.
May 08, 2014, 10:53:14 AM
Something to be aware of ==> http://www.reddit.com/r/litecoinmining/comments/216ydt/psa_possible_miner_exploit/
I don't see how this could be abused in NiceHash scenario. To be able to redirect miners, you either have to hijack domain or stratum server. Spoofed TCP packets might be oriented towards certain victim only - if you know it's IP. To get list of IPs of all miners on NiceHash, you need access to stratum server.
We don't ever send reconnect to any other pool, we use param-less reconnect method, which should result in miner connecting to same host. This has been documented already.
For all implementing your own extranonce subscriptions, here is proposed stratum extension RFC, which is currently being used:
Quote
Uppon successful subscription to stratum with "mining.subscribe" method, client should
send "mining.subscribe.extranonce" method.
{"id": X, "method": "mining.subscribe.extranonce", "params": []}\n
This informs the server (pool) that client (miner) supports extranonce1 change on-the-fly without the need to reestablish connection.
Servers supporting this method will reply:
{"id": X, "result": true, "error": null}\n
If the server does not support method, reply will be:
{"id": X, "result": false, "error": [20, "Not supported.", null]}\n
Server may also simply ignore this subscription and return no reply or return invalid method. Some pools may return incorrectly formed error message. Some pools may drop connection (in such cases, it is best to offer user a way to turn extranonce subscriptions off for certain pools - via config for example).
In all cases, client does not perform any logic when receiving back these replies.
With mining.subscribe.extranonce subscription, client should handle extranonce1 changes correctly.
Server would send:
{"id": null, "method": "mining.set_extranonce", "params": ["08000002", 4]}\n
First parameter is string extranonce1 value, second parameter is integer value of extranonce2 size.
Miner shall start using new extranonce1 when new job is provided with mining.notify.
send "mining.subscribe.extranonce" method.
{"id": X, "method": "mining.subscribe.extranonce", "params": []}\n
This informs the server (pool) that client (miner) supports extranonce1 change on-the-fly without the need to reestablish connection.
Servers supporting this method will reply:
{"id": X, "result": true, "error": null}\n
If the server does not support method, reply will be:
{"id": X, "result": false, "error": [20, "Not supported.", null]}\n
Server may also simply ignore this subscription and return no reply or return invalid method. Some pools may return incorrectly formed error message. Some pools may drop connection (in such cases, it is best to offer user a way to turn extranonce subscriptions off for certain pools - via config for example).
In all cases, client does not perform any logic when receiving back these replies.
With mining.subscribe.extranonce subscription, client should handle extranonce1 changes correctly.
Server would send:
{"id": null, "method": "mining.set_extranonce", "params": ["08000002", 4]}\n
First parameter is string extranonce1 value, second parameter is integer value of extranonce2 size.
Miner shall start using new extranonce1 when new job is provided with mining.notify.
May 08, 2014, 08:46:39 AM
Something to be aware of ==> http://www.reddit.com/r/litecoinmining/comments/216ydt/psa_possible_miner_exploit/
May 08, 2014, 05:01:13 AM
@Nicehash staff, I think you are abusing of the stratum method "client.reconnect". Why are you sending this? Is it really needed? It adds trouble to the stratum/tcp connection and some extra delays.
Reconnects are needed, because the stratum protocol does not implement a way to change special extranonce parameters except for on first connection. Switching between other pool's relays requires changing these parameters. You can use the patches or patched compiled cgminer that nicehashdev has posted and are available on git. This implements a new command in the stratum protocol so that the reconnects are not necessary.I see. However if I'm not wrong the client.reconnect method needs host and port parameters. The nicehash stratum server is not providing them, so it makes some system crash.
I'm not using sgminer/cgminer directly, I'm using a stratum proxy instead. Can you provide the specification on this new command so I can implement it in the stratum proxy?
May 08, 2014, 04:40:57 AM
For anybody who is interested, this device was supplied and is hosted by user pcfli https://bitcointalksearch.org/user/pcfli-253683
Jump to: