Author

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

full member
Activity: 202
Merit: 100
Anyone else seems to be getting disconnected frequently? Global stats on the site seems to be dropping down to 0GH/s at times the past hour.
trc
full member
Activity: 164
Merit: 100
This is so much more convenient than fixing the price a few times a day, watching for any downtime to compensate customers for and also dealing with scum not sending the funds after hitting the rent button at - you know where.

A well thought out, proper service with integrated wallet. Thank you!
sr. member
Activity: 252
Merit: 250
And the whitecoin dump begins!
sr. member
Activity: 266
Merit: 250
Whitecoin, I bet. Current profitability 0.01473849BTC/MH/DAY.
member
Activity: 107
Merit: 10
So what are all the buyers mining at the moment?  Looks expensive at the moment
hero member
Activity: 686
Merit: 500
I interpret the p = 6.1 (or anything else) as a fixed number meaning not lower, not higher.

Are you saying it is a minimum of some sorts?
Of course it is a minimum...

Exactly. If you set your p to let's say p=5 you will mine on orders paying 5 BTC/gh/day or better (round-robin fair system, see my previous posts about this). This is an unique feature for you to avoid falling below straight LTC mining (which often happens on various multi pools). Just don't be too greedy by setting to p to high otherwise you'll be throwing money away. phzi showed an excellent example of configuration of optimal high-to-low priority settings, just use your immagination, NiceHash brought to you a nice toy to play with Wink

Thnx for the answer.
Kenshirothefist send me a personal message asking about my question and gave me a perfect understandable explanation  Grin
Very nice and good service! Thank you  Grin
sr. member
Activity: 457
Merit: 273
Sellers/providers, can now see statistics for past 7 days.
hero member
Activity: 700
Merit: 500
The system paid out 25 minutes ago, but I got nothing and it says transaction not found.

Date               UTC         TXID                                                                                                 Amount BTC     Fee BTC
2014-04-19     00:07:22   9edb382d0cd9b3fbbf2394cb7093608ebff87b055e038a631bba98c62de7eda6   0.00613913     0.00012529
My node sees this TXID without any issue.  blockchain just hasn't picked it up yet, and it hasn't been included in a block.

Just be patient.
newbie
Activity: 44
Merit: 0
Just went through. Thanks
full member
Activity: 230
Merit: 100
What's going on with all the numerous dead orders?
newbie
Activity: 44
Merit: 0
now that the endless cycling is fixed im facing a new problem.

now sgminer think there is work available, disconnects current session. connects to nicehash, successfully sends about 12 shares. then disconnects and marks it as down and goes back to backup poool.

this would be ok if there was work, but it has been cyling like this constantly for about 3 hours now

Mine seems to be doing this as well.
newbie
Activity: 45
Merit: 0
now that the endless cycling is fixed im facing a new problem.

now sgminer think there is work available, disconnects current session. connects to nicehash, successfully sends about 12 shares. then disconnects and marks it as down and goes back to backup poool.

this would be ok if there was work, but it has been cyling like this constantly for about 3 hours now
sr. member
Activity: 457
Merit: 273
I interpret the p = 6.1 (or anything else) as a fixed number meaning not lower, not higher.

Are you saying it is a minimum of some sorts?
Of course it is a minimum...

Exactly. If you set your p to let's say p=5 you will mine on orders paying 5 BTC/gh/day or better (round-robin fair system, see my previous posts about this). This is an unique feature for you to avoid falling below straight LTC mining (which often happens on various multi pools). Just don't be too greedy by setting to p to high otherwise you'll be throwing money away. phzi showed an excellent example of configuration of optimal high-to-low priority settings, just use your immagination, NiceHash brought to you a nice toy to play with Wink
sr. member
Activity: 457
Merit: 273
You can already do this to some extent with the latest sgminer compiled from git.  No need to restart the miner or script anything.  sgminer now supports kernel hotswapping between different algorithms, and the hotswap takes less then a second.  So, you can setup your pool config like below to automatically switch between scrypt and nscrypt, and within a small margin or error mine the more profitable algorithm:

phzi, thanks for this, I wasn't aware of this sgminer capability. Great, than we alreday have the world's first true auto-switching multi-algorithm multi-pool Wink Go spread the word Wink
sr. member
Activity: 457
Merit: 273
What the hell just happened to your website? xD

Hell, I don't even need my monitoring system anymore since I get a post on this thread before an SMS message rings on my phone  Tongue

Guys, we are adding new features constantly therefor you'll see website down from time to time (application servers have to be restarted for certain upgrades to take place) ... Will do our best to get the maximum possible uptime. Thanks!
sr. member
Activity: 252
Merit: 250
What the hell just happened to your website? xD


newbie
Activity: 44
Merit: 0
The past few hours the connection has been dropping down to my backup pool. It seems to do it every time a new work order is completed.
hero member
Activity: 700
Merit: 500
This is why NiceHash can be attractive to you as a provider/seller: NiceHash will actually become a true multi-algorithm multi-pool where provider will be able to switch algorithm just by restarting his miner with different settings. This way you'll be able to see your earning all at one place, at NiceHash Wink

In the future we'll provide an API for the sellers as well as for the buyers to be able to automate miners switching and orders switching.

As a miner you'll be able to query our API and decide on which algorithm to point your miners in dependence of current orders profitability (if you can do a bit of scripting you can fully automate your miners to switch algos).
You can already do this to some extent with the latest sgminer compiled from git.  No need to restart the miner or script anything.  sgminer now supports kernel hotswapping between different algorithms, and the hotswap takes less then a second.  So, you can setup your pool config like below to automatically switch between scrypt and nscrypt, and within a small margin or error mine the more profitable algorithm:
Code:
        {
                "name" : "NiceHash SCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3333",
                "user" : "",
                "pass" : "p=10.0;d=512"
        },
        {
                "name" : "NiceHash NSCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3335",
                "user" : "",
                "pass" : "p=19.0;d=512",
                "algorithm" : "nscrypt",
                "nfactor" : "11"
        },
        {
                "name" : "NiceHash SCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3333",
                "user" : "",
                "pass" : "p=8.0;d=512"
        },
        {
                "name" : "NiceHash NSCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3335",
                "user" : "",
                "pass" : "p=15.0;d=512",
                "algorithm" : "nscrypt",
                "nfactor" : "11"
        },
        {
                "name" : "NiceHash SCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3333",
                "user" : "",
                "pass" : "p=7.0;d=512"
        },
        {
                "name" : "NiceHash NSCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3335",
                "user" : "",
                "pass" : "p=13.0;d=512",
                "algorithm" : "nscrypt",
                "nfactor" : "11"
        },
        {
                "name" : "NiceHash SCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3333",
                "user" : "",
                "pass" : "p=6.0;d=512"
        },
        {
                "name" : "NiceHash NSCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3335",
                "user" : "",
                "pass" : "p=11.0;d=512",
                "algorithm" : "nscrypt",
                "nfactor" : "11"
        },
        {
                "name" : "NiceHash SCRYPT",
                "url" : "stratum+tcp://stratum.nicehash.com:3333",
                "user" : "",
                "pass" : "p=5.5;d=512"
        }

I interpret the p = 6.1 (or anything else) as a fixed number meaning not lower, not higher.

Are you saying it is a minimum of some sorts?
Of course it is a minimum...
legendary
Activity: 3654
Merit: 8909
https://bpip.org
I interpret the p = 6.1 (or anything else) as a fixed number meaning not lower, not higher.

Are you saying it is a minimum of some sorts?

https://nicehash.com/index.jsp?p=faq#faqs3
hero member
Activity: 686
Merit: 500


I think nicehash should put everyone with the p= parameter in the same round-robin like everyone else. E.g. when it's your turn to get switched to a lower price, because of the p= you disconnect and go to your backup pool. Once it's your turn to mine the higher price, you can connect again. If that's not how it works then it's a major flaw.
[/quote]

That would be great.
Jump to: