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

[pzero15]

I'm trying the x13 algo with sgminer 5.0, but with the following command line, my prompt window is closing on startup.

setx GPU_MAX_ALLOC_PERCENT 100
del *.bin
sgminer -k marucoin -o stratum+tcp://stratum.nicehash.com:3337 -u BTC_ADDR -p x -I 13 -g 2 -w 256 --thread-concurrency 8192 --api-listen --api-allow W:127.0.0.1

**even the marucoin-mod is doing the same thing.

Thanks for your help

ad -T in your batch file. should pause on errors. than you can see what is at fault.

OK so "-k" is not a recognized command. How do we specify the mining kernel in sgminer 5.0 ?
PS: "-T" doesnt work so I put a "pause" line.

[kenshirothefist]

Providers and buyers, NiceHash brought you another innovation: NiceHash.com Best Profit Auto-Switching Multi-Algorithm GPU Mining. You can get more information here: https://www.nicehash.com/multialgo/

[suchmoon]

Providers and buyers, NiceHash brought you another innovation: NiceHash.com Best Profit Auto-Switching Multi-Algorithm GPU Mining. You can get more information here: https://www.nicehash.com/multialgo/

"A" for the effort, but I think you are going the wrong route here. Hashrate ratio needs to be configurable. For example with X11 I can get 4.2 on some cards and 3.5 on others, not to mention power consumption. I'm also not sure why you put all that into pool config. It would be much cleaner to have algo-specific parameters (thread-concurrency etc) defined separately from pools and work on a stratum implementation that allows switching without redefining the same pool over and over again. What happens if another multipool decides to implement something similar? How many pool definitions would I end up with if just wanted main pool + two failovers? 3 times the number of algorithms? This doesn't seem to scale.

[nicehashdev]

There is no stratum protocol specification that would allow on-the-fly algorithm change without reconnect.

But if that happens, and if the stratum is a bit reorganized - so the auth handshaking is performed FIRST and then mining begins (not vice verse like now), then we have a chance to implement something similar as you suggested.

Keep in mind that we wanted to make it simple. Simplicity has proven to work in this scene, where people rather get paid less, as long as they don't have to work so much. The current needed work is only to put pools into your config, the rest is done by us.

[suchmoon]

There is no stratum protocol specification that would allow on-the-fly algorithm change without reconnect.

But if that happens, and if the stratum is a bit reorganized - so the auth handshaking is performed FIRST and then mining begins (not vice verse like now), then we have a chance to implement something similar as you suggested.

Keep in mind that we wanted to make it simple. Simplicity has proven to work in this scene, where people rather get paid less, as long as they don't have to work so much. The current needed work is only to put pools into your config, the rest is done by us.

Don't get me wrong, I understand this is just a start and I'll be definitely be testing it. I have to disagree though with defining algo-specific parameters for each pool. It would be just as simple to have a section for algorithms/kernels/whatever:

"algorithms": [
     {
          "name" : "scrypt",
          "kernel" : "zuikkis",
          "nfactor" : "10",
          "gpu-engine" : "1000",
          "thread-concurrency" : "8192"
     },
...

and then just reference it in the pool config:

"pools": [
     {
          "name" : "NiceHash_Scrypt_multi",
          "url" : "stratum+tcp://stratum.nicehash.com:4333",
          "user" : "BTC_address",
          "pass" : "d=1024",
          "algorithm" : "scrypt"
     },

It's simple, clean, and reusable for more than just nicehash. I just don't see why thread-concurrency and other parameters need to be pool-specific.

[nicehashdev]

It's simple, clean, and reusable for more than just nicehash. I just don't see why thread-concurrency and other parameters need to be pool-specific.

That is how creators of newest sgminer did it. I don't recall this being done like it is on our request.

[gargouri2001]

Hello there

What rate are u people getting right now per 1 mhash

Thanks

[nicehashdev]

Hello there

What rate are u people getting right now per 1 mhash

Thanks

3.6696 BTC/GH/Day right now if you use multi-algo mining.

[gargouri2001]

Hello there

What rate are u people getting right now per 1 mhash

Thanks

3.6696 BTC/GH/Day right now if you use multi-algo mining.

so it is 0.00358 per 1 mhash almost twice better than clevermining , worth a try
thanks for info

[pzero15]

I'm trying the x13 algo with sgminer 5.0, but with the following command line, my prompt window is closing on startup.

setx GPU_MAX_ALLOC_PERCENT 100
del *.bin
sgminer -k marucoin -o stratum+tcp://stratum.nicehash.com:3337 -u BTC_ADDR -p x -I 13 -g 2 -w 256 --thread-concurrency 8192 --api-listen --api-allow W:127.0.0.1

**even the marucoin-mod is doing the same thing.

Thanks for your help

ad -T in your batch file. should pause on errors. than you can see what is at fault.

OK so "-k" is not a recognized command. How do we specify the mining kernel in sgminer 5.0 ?
PS: "-T" doesnt work so I put a "pause" line.

Anyone?

[odie158]

I am having trouble figuring out the multi algorithm thing. I cut and pasted the example config file into a text document that I named sgminer.conf. when I start sgminer it says Fatal JSON error in config file and doesn't work. I usually use cgminer. I am running a single gigabyte 7950

[azzman372]

OK so "-k" is not a recognized command. How do we specify the mining kernel in sgminer 5.0 ?
PS: "-T" doesnt work so I put a "pause" line.

Anyone?

To specify the kernel, use --algorithm marucoin for x13

Also I found that there is an issue with the example config file on the nicehash page. There is an extra comma which causes sgminer to not load the config file. This seems to be fixed as of now but the extra comma was just before the ] after the {. I removed it and it was fine.

I do seem to be running into an issue with the config file tho. When I try to run just one pool for testing (x11) using the config file, sgminer seems to never submit any work.
However running the equivalent command line, it is working fine

config file:

Code:

{
"pools" : [
     {
          "name" : "NiceHash_X11_multi",
          "url" : "stratum+tcp://stratum.nicehash.com:3336",
          "user" : "x",
          "pass" : "d=0.01",
          "pool-algorithm" : "darkcoin-mod",
          "pool-thread-concurrency" : "15232",
	  "pool-gpu-threads" : "2",
	  "pool-intensity" : "18"
     }
],
"failover-only" : true,
"failover-switch-delay" : "30",
"device" : "1"
}

command line:

Code:

sgminer.exe --algorithm darkcoin-mod -d 1 -o stratum+tcp://stratum.nicehash.com:3336 -u x -p d=0.01 -I 18 -w 512 -g 2 --thread-concurrency 15232

[nemesio]

I am having trouble figuring out the multi algorithm thing. I cut and pasted the example config file into a text document that I named sgminer.conf. when I start sgminer it says Fatal JSON error in config file and doesn't work. I usually use cgminer. I am running a single gigabyte 7950

last line in the example config isn't part of a working config, make sure you deleted.

Also, make sure everything has commas where appropriate.

[spiderdk]

Multi algorithm not working here, any clea path to configure it? Preferable with cgwatcher

[brucen]

The BPASMAM is working well for me after I tested and tuned each pool. However the Keccek_multi pool is showing some problems. I'm getting around 40% rejects (Job not found) and I'm also seeing an occasional GPU invalid nonce count - HW error. Anyone else seeing these issues with the Keccak algo?

[guzzzi]

Anyone know what the +/- max Hash for a 290x

scrypt - 880-1000+
nscrypt - 400-450+
x11 - 4000-4500
x13 - ?
keccak - ?

and maybe some good configs for keccak? trying the multi-algo.

[pzero15]

OK so "-k" is not a recognized command. How do we specify the mining kernel in sgminer 5.0 ?
PS: "-T" doesnt work so I put a "pause" line.

Anyone?

To specify the kernel, use --algorithm marucoin for x13

Also I found that there is an issue with the example config file on the nicehash page. There is an extra comma which causes sgminer to not load the config file. This seems to be fixed as of now but the extra comma was just before the ] after the {. I removed it and it was fine.

I do seem to be running into an issue with the config file tho. When I try to run just one pool for testing (x11) using the config file, sgminer seems to never submit any work.
However running the equivalent command line, it is working fine

config file:

Code:

{
"pools" : [
     {
          "name" : "NiceHash_X11_multi",
          "url" : "stratum+tcp://stratum.nicehash.com:3336",
          "user" : "x",
          "pass" : "d=0.01",
          "pool-algorithm" : "darkcoin-mod",
          "pool-thread-concurrency" : "15232",
	  "pool-gpu-threads" : "2",
	  "pool-intensity" : "18"
     }
],
"failover-only" : true,
"failover-switch-delay" : "30",
"device" : "1"
}

command line:

Code:

sgminer.exe --algorithm darkcoin-mod -d 1 -o stratum+tcp://stratum.nicehash.com:3336 -u x -p d=0.01 -I 18 -w 512 -g 2 --thread-concurrency 15232

Thank you very much for you help ! It works now.

[suchmoon]

It's simple, clean, and reusable for more than just nicehash. I just don't see why thread-concurrency and other parameters need to be pool-specific.

That is how creators of newest sgminer did it. I don't recall this being done like it is on our request.

The way I read this: https://bitcointalk.org/index.php?topic=632503.0;topicseen is that nicehash had significant involvement in that development. Not that it matters to me one bit, I'm just surprised to see that kind of a hack in an otherwise decent piece of software.

[guzzzi]

Getting always diff 0.000 when try the multi-aglo routine with the new sgminer Version from the NH Website. Is that normal?

[nicehashdev]

Getting always diff 0.000 when try the multi-aglo routine with the new sgminer Version from the NH Website. Is that normal?

If you get accepted shares and you can see stats on NiceHash for your miner(s), then completely normal and nothing to worry about.