Topic: [PPS multipool] NiceHash.com pool - higher profits than direct mining BTC! - page 20. (Read 98715 times)

Your wording was clearly choosing a scapegoat ... since you claimed the hardware and miner were at fault but provided no details of why the hardware or the miner were at fault.

Mining just BTC works fine.

As soon as you add merged mining that prioritises the merged mined coin above the BTC mining, to either make "extra profit" for you, or "extra payout" for your clients, of those merge mined coins, the result is loss of shares on BTC.

3 second restarts means that the merged mined coins are getting priority over the BTC restarts and miners are losing BTC.
Sounds like a REALLY bad idea to me ...

It works for me just as advertised and shown on front page. Like I said before.

ckolivas, we respect you as a cgminer developer and overall contributor to Bitcoin community and we are not looking for any scapegoats here ... we're just trying to run a service where both - owners of the mining devices and those who are seeking for hashing power to rent - can benefit. We'll continue to work with hardware and software providers to make sure that various crypto coins (not all of them are shitcoins) will be mineable by various mining devices.

Scrypt miners have nothing to do with this, and I object to you blaming cgminer or the hardware for these issues. 3 second restarts will cause a loss of 10-15% of hashrate no matter how powerful the controller. You are mining shitcoins and miners are losing income as a result, thinking the bonuses will make up for it somehow.  Being aware of the issues and planning to tackle them is good but please choose your scapegoats wisely.

Buyers of hashing power at NiceHash/WestHash are not only mining Bitcoin, they are also (sometimes) mining various other coins. Some of them are still at very low difficulty, switching jobs very fast, etc. Unfortunately manufacturers of ASIC miners are putting very weak controllers in their miners (saving a few $ in a machine, worth hundreds even thousands of $ ) with non-optimized software and are thus unable to process large number of shares/jobs/work-restarts. A typical example was KnC Titan (not SHA256, but an Scrypt miner) which was only able to mine Litecoins until the controller software was properly optimized. Recent example of a SHA256 miner that is having a few issues with rejects is AntMiner S5, hopefully Bitmain will improve it soon. If manufacturers would put a multi-core Raspberry Pie 2 in their miners (with a good controller software - I'm not talking only about cgminer/bfgminer, but also drivers, etc. handling of low difficulty coins, switching jobs very fast, proper handling of flushwork, etc.) there would be no issues. For example, there are no issues with sgminer mining any GPU based coin, running on PC (which always has a decent CPU). Probably there is also room for improvement in cgminer itself for these issues.

Anyway, we are aware of these issues and we've implemented measures to mitigate these issues a long time ago. We are rewarding providers (sellers) with extra shares paid by buyers when fast work restarts happens. If you are a seller it is very important for you to monitor the average mid-term hashrate, reported on our website (it is calculated from shares, rewarded to your miner) and the actual earnings, not only the hashrate or accept/reject ratio that is displayed by your miner hardware/software, since in some cases you will be rewarded for more then your miner is showing you in terms of hashrate. Details are explained in this FAQ.

Since nicehash is actually a proxy pool, you are not mining directly on the actual upstream pool. You are assuming there is no hit to performance by doing this. I've been trying to help someone with a large farm debug why they take a massive reject hit which far more than offsets the fee at certain times on nicehash and the fact it's a proxy pool is the only valid explanation. I've seen it do some funky mining with restarts every 3 seconds - no mining hardware can work efficiently with that.

I have been mining on this pool for months now and I must admin, no issues so far. Payments are regular.

I simply don't understand why bother mining elsewhere. If you look at the 30 day chart, you see that NiceHash pays 1.5% more than Bitcoin mining. It is pay per share pool and it has 2% fee. That makes it -0.5% less than Bitcoin mining or in other words - as a 0.5% fee PPS pool. No other pool can survive this on long term. And I didn't consider the 10 fold payment increase that lasted whole week in december.

I don't even set p parameter. Because on long term, NiceHash pays more and additional pool switching just causes troubles with my antminers.

Whoever thinks that there are better paying pools out there should do the math and recalculate again.

Again there are currently some very well paying orders. Past 7 days average price is also good: +5% more then direct Bitcoin mining. You are welcome to join our service.

Look for a p2pool node near you. Set your miners and wait and be patient.

I've had 3 miners pointed to NiceHash/WestHash for when the payout is >3% above BTC and using BitAffNet as a secondary for the lower payout times and it has worked well until BitAffNet stopped paying (It's been over a week since payout and they just retroactively adjusted the payout to the new difficulty resulting in a 7.71% loss!).  I'm now looking for a new pool(s) for my secondary on these 3 miners since I'm done with BAN.

If I stick with PPS, I'm probably looking at a 4% pool and I'd set WestHash to 2% below BTC.  I'm not certain if this is the best (most profitable) approach though.

For those with experience doing so, how well does hopping on/off WestHash work with a PPLNS pool?  It would seem that with high N value it would even out, but the variance does make it difficult to determine.  Maybe speading out across multiple PPLNS pools could reduce the variance/risk from switching on/off WestHash?

What is a good value to set WestHash at when using along with PPLNS?

It happened for a week back in December due to GAW launching the PoW phase of their coin.  People were paying outrageous prices to get gear to mine that coin which was supposed to have a $20 value floor.  That didn't hold for more than 30 minutes when the official GAW exchange opened up.

Anyway, I don't intend to drag this thread into the myriad others already discussing GAW and their coin, but I wanted to point out how it is that folks with gear on nice/westhash were indeed making 1000% during that timeframe .

Exactly! And you can make use of our fresh NiceHashBot which will help you sustain desired hashing power with a minimum effort and best price: https://github.com/nicehash/NiceHashBot

Rent some power and point it to this solo pool https://bitcointalksearch.org/topic/yh-solockpoolorg-2-fee-solo-mining-usade-255-blocks-solved-763510 to have a chance to win 25BTC

Usually you can rent out and get right at the projected BTC yield. That is better than any regular BTC pool is doing these days. Renting is usually done by people chasing pumped coins. Last week it was UNB.

Is it really worth buying hashing power or its just a 100 percent loss ?

I just started using that site and I am lost.

[BTC +1000%] Try NiceHash.com pool, INSANE Bitcoin up to +1000% profits atm!!!

yea right BS!

I would like to know how to achieve that if it's legit which I doubt it sounds like a big fat ponzi scheme!

Thanks for the reply. I have tried using this exact address : stratum+tcp://stratum.nicehash.com:3334 , but I have never tried the extranonce. I have 4 S3's on Westhash right now, and they will all connect with or without the extra // prefix on the address. The Bitcoin address is definitely valid, it is the same one that the S3's are using. My miners are numbered 11-15, so I have the addition of worker on the end of address (Bitcoinaddress.11-.15) and I have also tried using no suffix on the S5 bitcoin address, as well as trying one of the other address's with a different suffix with no luck. I am stumped on this one, although I have a feeling it is something simple to fix.

Edit to add: Are you saying I should enter this entire address(including the stratum+tcp:)into the address bar on the S5? stratum+tcp://stratum.nicehash.com:3334


Edit again: I used the entire address including the stratum+tcp: prefix and it worked!





Solved! I figured it was something simple. Very strange that the S5 will not connect using the address without the stratum+tcp prefix but the S3's will.

Hi,

Try specifically add stratum+tcp at the beginning of the pool string, exactly like this:


stratum+tcp://stratum.nicehash.com:3334#xnsub

or

stratum+tcp://stratum.westhash.com:3334#xnsub


(#xnsub parameter at the end enables extranonce.subcribe for better efficiency on our service)

Also, make absolutely sure you're using valid Bitcoin address for Worker name, validate it through https://blockchain.info/ Search field.


This should work. Also, are you using these S5 miners on the same location with the same public IP address as other miners of yours, which are running fine on WestHash/NiceHash?

These settings work on all of my S3's. I have tried address with and without the //, pay limit password and no password (x), everything I could think of and I can not get my S5 to accept Westhash (or Nicehash). Always shows as dead.

screen shot the settings

what is the top setting.


stratum+tcp://stratum.westhash.com:3334   = pool


btc address                                                 = user



P=0.0102                                                    =   password set to a price  try a really low price like the one on the left.