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

pzero15

newbie

Activity: 16

Merit: 0

Quote from: pzero15 on June 03, 2014, 08:05:44 AM

Quote from: ?? on ??

Quote from: pzero15 on June 03, 2014, 07:29:30 AM

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?

gargouri2001

full member

Activity: 210

Merit: 100

Quote from: nicehashdev on June 03, 2014, 05:39:31 PM

Quote from: gargouri2001 on June 03, 2014, 05:03:53 PM

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

nicehashdev

sr. member

Activity: 280

Merit: 250

Quote from: gargouri2001 on June 03, 2014, 05:03:53 PM

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

full member

Activity: 210

Merit: 100

Hello there

What rate are u people getting right now per 1 mhash

Thanks

nicehashdev

sr. member

Activity: 280

Merit: 250

Quote from: suchmoon on June 03, 2014, 02:55:37 PM

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.

suchmoon

legendary

Activity: 3654

Merit: 8909

https://bpip.org

Quote from: nicehashdev on June 03, 2014, 02:35:00 PM

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

sr. member

Activity: 280

Merit: 250

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

legendary

Activity: 3654

Merit: 8909

https://bpip.org

Quote from: kenshirothefist on June 03, 2014, 01:28:21 PM

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.

kenshirothefist

sr. member

Activity: 457

Merit: 273

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/

pzero15

newbie

Activity: 16

Merit: 0

Quote from: ?? on ??

Quote from: pzero15 on June 03, 2014, 07:29:30 AM

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.

pzero15

newbie

Activity: 16

Merit: 0

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

kenshirothefist

sr. member

Activity: 457

Merit: 273

Fresh builds of sgminer-5 are available: https://nicehash.com/software/#sgminer (x13mod has been added).

Note: darkcoin and darkcoin-mod represents x11 and x11mod (optimized), respectively; marucoin and marucoin-mod represents x13 and x13mod (optimized), respectively.

Note: hd5xxx/6xxx still have problems with marucoin-mod (x13mod), but lasybear is working on it, I guess it will be fixed soon.

odie158

member

Activity: 85

Merit: 10

Quote from: odie158 on June 02, 2014, 06:02:07 PM

Terrible!!! First your "upgrade" allowed new orders to be qued above older ones and you didn't return them to the proper order. Now you add another decimal place allowing people to place orders at a small fraction above what someone else placed an order at weeks ago at an expected interval.
I placed my order at .04 and .03 when ordinary pools were still paying over .05 knowing that patience would yield me an arbitrage. By first refusing to fix the error caused by your "upgrade" and now allowing others to place orders at a small fraction above my orders you have stolden that opportunity.
The proper way to handle the adding of another decimal place would have been to close to new orders and allowed existing orders to be filled and only then added more decimal places and reopen for orders. As it is you have effectively ripped everyone with an order smaller than .05 off

Ok, I feel better after my rant. Nice hash is trying very hard to provide a quality product and I am quite happy with the returns that I am receiving on my sold hashing power. I an sad because if the queing mistake not been made I would've already made 20% return simply by using the service. I am sure that even under the current circumstances I will make an acceptable return.

odie158

member

Activity: 85

Merit: 10

Terrible!!! First your "upgrade" allowed new orders to be qued above older ones and you didn't return them to the proper order. Now you add another decimal place allowing people to place orders at a small fraction above what someone else placed an order at weeks ago at an expected interval.
I placed my order at .04 and .03 when ordinary pools were still paying over .05 knowing that patience would yield me an arbitrage. By first refusing to fix the error caused by your "upgrade" and now allowing others to place orders at a small fraction above my orders you have stolden that opportunity.
The proper way to handle the adding of another decimal place would have been to close to new orders and allowed existing orders to be filled and only then added more decimal places and reopen for orders. As it is you have effectively ripped everyone with an order smaller than .05 off

kenshirothefist

sr. member

Activity: 457

Merit: 273

OK, some good news here, for both providers and buyers.

1.) X13 and Keccak (SHA3) algorithms have been added.

2.) Builds of the brand new sgminer-5 are available: https://nicehash.com/software/#sgminer (more info here: https://bitcointalk.org/index.php?topic=632503.0); you can use this sgminer for all algorithms, supported by NiceHash (except SHA256, of course).

Thanks for using NiceHash!

trc

full member

Activity: 164

Merit: 100

Quote from: nicetry on May 31, 2014, 10:47:29 PM

actually people mentioned in the forums that nicehash got problems with multipools, but if we can't use it with multipools, then what good is it? Blackcoinpool server is actually US based. So i don't see why nicehash would have problem connecting to it.

I've asked this to some pool admins in their IRCs and they advise to put a limit on the rented speed. This depends on the pool but usually around 0.3gh/s per worker.
Those that go unavailable(red) while waiting in the queue don't like to keep an open connection without any work requests and some pools don't want to change this behavior. Understandably, to save bandwidth(less likely) or minimize attack risk I guess.

aagert

sr. member

Activity: 330

Merit: 250

📱 Electroneum 📱 cryptocurrency

nicehashdev,
looks like you have charts component linked to your service via external API (google's?), right? I'm assuming that because often text stats are loading extremely fast, but charts load takes forever with "Waiting for google.com" in browser status line. Could you just download that component and load it from your own server instead of external?

kaisersto

newbie

Activity: 3

Merit: 0

Have been using nicehash for about two days now, and really impressed so far. Have approx 3.9mh pointed at it and the returns look good, very good, so far.
I have a black widow from gawminers hopefully arriving soon, so will also add that to the hash rate.

Deathwing

legendary

Activity: 1638

Merit: 1329

Stultorum infinitus est numerus

Quote from: guzzzi on June 01, 2014, 10:59:13 AM

Tryed x11 but getting a lot of

Stratum from Pool 0 requested work restart

Anyone know how to fix this?

It's normal.

guzzzi

newbie

Activity: 53

Merit: 0

Tryed x11 but getting a lot of

Stratum from Pool 0 requested work restart

Anyone know how to fix this?

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