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

no i just have the regular firmware from bitmain..
my s5 works tho and has a check.. and yeah i am putting it after the port.. like this
stratum+tcp://stratum.westhash.com:3334#xnsub

so it looks like to get the s3s to work i need to make my own proxy? or just leave it?

Are you putting /#xnsub before the port number? I did that too. It goes after.

i.e: http://www.nicehash.com:port/#xnsub

Also, unless you have a modified version of CGMiner flashed to the S3 it won't work anyway.

if i put #xnsub on my s3s the pool shows up as down.. do they not support it?

Past 7 days almost 5% higher profit than ideal 100% luck bitcoin mining!

I have mine set a bit higher because I have had problems a couple of times with miners failing back over to my other pools and for the risk of that happening again I want to only rent if it's worth my while. And in case we get another run like the PayCoin I don't want to miss it.

im going to step in here because the last two pages of this thread are just getting silly.

1) not sure why you keep attacking kano directly. its unneccessary, and makes you look like an ass (same goes for kano responding in a similar manor)
2) LUCK: "success or failure apparently brought by chance rather than through one's own actions"  //OR//   "chance to find or acquire"
-luck (or 'varience') is unpredictable, and always changing. A pool can have 85% payouts one week and 110% payouts the next. The priciple is that over a sufficienctly long period of time (months or years) the overall payout should be 100% (+/- a few %)
3) as such, the luck you see TODAY is not what you will see TOMORROW. It changes. basic probability and statistics says so.

4) why would you put less than the going BTC/TH/day into nicehash calculations? The best method for nicehash is to set it ~3% higher than the "typical/predicted" payout of other pools, so that your miner switches only when it is sufficiently profitable.

Lulz more crap being spouted by this fool.
Nowhere did I say all pools pay 100%.

Yep guess what, you have to subtract pool fees and expected orphans.
I wonder if you know what subtraction is though, I better give you a link: http://en.wikipedia.org/wiki/Subtraction

And yet again with the "Expected pool average payout is 90%" - lulz you're so ignorant.

Heh, luck since my pool started has totalled almost 105% and the last 10 block luck has been almost 107% (last 5 is currently 166% luck)

Hey maybe you should point out how the OP post above is also wrong suggesting people set it above 100% - not 90% as you keep telling anyone stupid enough to take any notice of you (though I doubt anyone is that stupid)

For past few days, NiceHash/WestHash has been paying several percents above ideal 100% luck Bitcoin mining. We suggest you to join mining now until this high price lasts!

Not if you want to maximize the potential of Nicehash. First off, you need to decide if you want to beat the average pool payout, or pretend that all pools pay 100%, as Kano suggested. A realistic average for pool payout (yes, I understand why, but thanks for flooding the thread with luck explanations ) is ~90% (some slightly more, some less) of that .01078, so ~.009 is what you will likely average from a pool over a month period. Then you need to factor in the time lost due to switching pools if you set at a higher rate compared to setting it right around or even slightly lower than that .009, and more importantly, the higher paying bids you will miss out on if you switch over too often. I have tried higher, same, slightly lower and no price cutoff using Nicehash/Westhash, and the best long term yield is setting it right near what your failover pool averages. You are of course quite free to choose your own method and ignore all of what I say, please do, I will certainly enjoy being able to scoop up more of the high bids for myself.

Completely agree. Dodgy pool run by a scammer.

I wouldn't touch BAN with a shitty stick 

I would no longer recommend BAN as a pool. Their payouts are getting worse. My payout is late going on 60+ hours. They are behind on over 100BTC in payments with all their blocks confirmed as they state on their pools website.

Our combined oustanding balance in queue to be paid is 115.34408460 Bitcoin.
There are 0 mined blocks waiting to mature, totalling 0 Bitcoin

dude you set over not under the bitcoinwisdom prediction.  you do it to  help prevent excessive switching.   

for now 0.01078   is 1 th a day.

 so do 0.0120  as in p = 0.0120

then use

 f2pool
kano's pool
or ban as second choice

Sigh, and I was hoping to not have to post any more.
But I wont stand for you posting lies about me.
Funny how instead of admitting you are wrong, you instead add more lies.

Nowhere have I attacked NiceHash in anything I've said, unless you are NiceHash?
Would the thread OP like to verify that indeed this fool is not NiceHash?
Pointing out the stupidity of listening to you is a good service to NiceHash customers.

Again stating that you think current pool luck will determine future pool luck.

And finally a rather important thing to understand from statistics (that no doubt you wont understand)
Sample vs Population

You are quite literally saying the same as:
I rolled a dice 18 times and got 4 threes.
Everyone else will roll 4 threes if they roll a dice 18 times.
Now lets see if you can see understand how stupid that is
Not sure if you can.
But if you do, then maybe you'll even realise you've said the equivalent of that repeatedly.

The best you can do is use the current rate of payout. Ancient history does not matter, but current luck, or lack thereof, is the only thing you can use. You are quite free to not look at current rates when choosing what pool to use, by all means, please go right ahead and use the one that is currently paying the least, be it due to luck or skimming or whatever.

P.S: In the future I will try not to share what works for me based on direct experience, I can see how well that works here when you have people trying to promote their own pools attacking you. I can however assure anyone who actually cares about getting the maximum return from their miners that my rates of payout using exactly the method described in that post are well above any of the pools I have personally tried on their own. Have a nice day, and by all means, Kano, continue attacking Nicehash in an effort to drive miners to your pool, that is pure class, bro!

Sorry, but the numbers aren't correct (in this context). If you take luck as a measurement you can only say what happened in the past. Pool luck is not a constant thing. It's going up and down all the time and there is no way in predicting the future luck.

Still trying to back out on what you said - lol.

Yet again I say go read my first 2 replies.
They are replies to the fact that you said something that was complete bullshit.
You said MOST pools are 85% to 90%
That is complete bullshit.

I would also actually point out that your suggested price cut off is also wrong.
Hopefully no one takes any notice of that crap from you and loses BTC because of it.

Now the last and most relevant point:
You are now quite explicitly saying that since Slush's luck for the past month produce an 85% payout for whatever that account was with the crappy payout, then all account on Slush will get that crappy 85% payout in the future.
That is just pure stupid lack of understanding mining.

I'd very much doubt anyone else would be stupid enough to not understand the facts I've stated and hopefully no one would be stupid enough to listen to you who wont back out when you screwed up and said something that is wrong.

I still have actually no idea where you could even come up with that rubbish stating that most pools are 85% to 90%.
You haven't anywhere backed up that statement with facts whatsoever. Cos there are none.

My first post on the subject still stands - those numbers are rubbish.

End of story. I've wasted too much time on this.

Edit: slush found 10 blocks in 12 hours today ... I rest my case.

Kano: The question posed by another member that I replied to was not asking about why pools have a certain rate of return compared to the predicted payout at a certain difficulty. He was asking what the best price point to rent his miners at here was and I told him, and those numbers are accurate. You said they were rubbish, and they are not. The best way to utilize Nicehash is to set your miner's password right at what the average payout of your failover pool is. As an example, Slush. Slush paid out 85% of the predicted yield last month.  You have gone on at length trying to explain why this is so (luck) , and that is simply not relevant. The fact is that miners on Slush were paid 85% of the predicted payout, therefore, if you want to maximize profits the best strategy for using Nicehash to do so is to set the price cutoff at the expected payout of your failover pool. That way , when bids that will pay higher than your failover pool are available you will get paid higher than you otherwise would. By the way, I actually understand the math behind calculating luck just fine, so your lengthy dissertation on this topic which was irrelevant to the question posed was wasted on me.

LOL - seriously, learn a bit about pools and payouts, so you can avoid giving incorrect advice to people.

Edit: and your reply above is a lie that you even missed that point that you yourself said "most" pools:
... "most" is why I replied in the first place if you actually bothered to read any of my replies ...

Full moon tonight?

What the fuck ever, Kano. My numbers are in fact correct when calculating what you will actually get paid when you compare that to the predicted payout. That is precisely what the poster was asking when I answered his question. Why you get paid a certain amount on different pools was not being discussed and you are just trying to obfuscate things by introducing strawman arguments.

 You should have just told me that you were running a pool and you were here to try to drive people away from here to your pool, it would have saved a lot of keystrokes.