Bitcoin Forum
February 20, 2019, 02:39:05 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 »  All
  Print  
Author Topic: [PPS multipool] NiceHash.com pool - higher profits than direct mining BTC!  (Read 81589 times)
Paul Revere
Sr. Member
****
Offline Offline

Activity: 406
Merit: 250


The Scamcoats are coming!


View Profile
March 24, 2015, 12:27:31 PM
 #121

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.

All of my posts are simply statements of my own personal opinions based on available information and pondering what might be possible considering human nature, with the goal of finding truth and preventing fraud. Please look at all of the facts and theories and put your thinking cap on to draw your own conclusions. If you feel that I have made a false statement or have been unnecessarily derogatory, I encourage you to please point it out, and if proven correct and/or reasonable I will remedy it. ~ Paul Revere
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1550630345
Hero Member
*
Offline Offline

Posts: 1550630345

View Profile Personal Message (Offline)

Ignore
1550630345
Reply with quote  #2

1550630345
Report to moderator
kano
Legendary
*
Offline Offline

Activity: 2730
Merit: 1103


Linux since 1997 RedHat 4


View Profile
March 24, 2015, 12:49:39 PM
Last edit: March 24, 2015, 01:12:34 PM by kano
 #122

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.
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.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
blumenkr4ft
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
March 24, 2015, 03:53:16 PM
 #123

My numbers are in fact correct when calculating what you will actually get paid when you compare that to the predicted payout.

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.

Paul Revere
Sr. Member
****
Offline Offline

Activity: 406
Merit: 250


The Scamcoats are coming!


View Profile
March 24, 2015, 07:00:22 PM
 #124

My numbers are in fact correct when calculating what you will actually get paid when you compare that to the predicted payout.

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.



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!

All of my posts are simply statements of my own personal opinions based on available information and pondering what might be possible considering human nature, with the goal of finding truth and preventing fraud. Please look at all of the facts and theories and put your thinking cap on to draw your own conclusions. If you feel that I have made a false statement or have been unnecessarily derogatory, I encourage you to please point it out, and if proven correct and/or reasonable I will remedy it. ~ Paul Revere
kano
Legendary
*
Offline Offline

Activity: 2730
Merit: 1103


Linux since 1997 RedHat 4


View Profile
March 24, 2015, 11:25:19 PM
 #125

My numbers are in fact correct when calculating what you will actually get paid when you compare that to the predicted payout.

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.



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!
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 Smiley
Not sure if you can.
But if you do, then maybe you'll even realise you've said the equivalent of that repeatedly.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
philipma1957
Legendary
*
Offline Offline

Activity: 2380
Merit: 1542


Avalon 841 rocks


View Profile
March 24, 2015, 11:33:15 PM
 #126

Where would you go to get a good price to input on the password line? I have an S5 that I want to try it out on. The C1's never worked with it at all unless I was mining %100 on Westhash.com.

I set it maybe 5-10% lower than the Coinwarz predicted return for 1 TH. The best pools average maybe 95% of predicted payout (most are usually more like 85-90% after you factor in the fee), so that is the price line you want to be above.

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

I mine alt coins with https://simplemining.net...
I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
aurel57
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000



View Profile
March 25, 2015, 01:23:52 AM
 #127

Where would you go to get a good price to input on the password line? I have an S5 that I want to try it out on. The C1's never worked with it at all unless I was mining %100 on Westhash.com.

I set it maybe 5-10% lower than the Coinwarz predicted return for 1 TH. The best pools average maybe 95% of predicted payout (most are usually more like 85-90% after you factor in the fee), so that is the price line you want to be above.

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

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
IYFTech
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500


WANTED: Active dev to fix & re-write p2pool in C


View Profile
March 25, 2015, 01:57:27 AM
 #128

I would no longer recommend BAN as a pool.

Completely agree. Dodgy pool run by a scammer.

I wouldn't touch BAN with a shitty stick  Cheesy

-- Smiley  Thank you for smoking  Smiley --  If you paid VAT to dogie for items you should read this thread:  https://bitcointalk.org/index.php?topic=1018906.0
Paul Revere
Sr. Member
****
Offline Offline

Activity: 406
Merit: 250


The Scamcoats are coming!


View Profile
March 25, 2015, 01:16:25 PM
 #129

Where would you go to get a good price to input on the password line? I have an S5 that I want to try it out on. The C1's never worked with it at all unless I was mining %100 on Westhash.com.

I set it maybe 5-10% lower than the Coinwarz predicted return for 1 TH. The best pools average maybe 95% of predicted payout (most are usually more like 85-90% after you factor in the fee), so that is the price line you want to be above.

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

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 Roll Eyes ) 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.

All of my posts are simply statements of my own personal opinions based on available information and pondering what might be possible considering human nature, with the goal of finding truth and preventing fraud. Please look at all of the facts and theories and put your thinking cap on to draw your own conclusions. If you feel that I have made a false statement or have been unnecessarily derogatory, I encourage you to please point it out, and if proven correct and/or reasonable I will remedy it. ~ Paul Revere
NiceHashSupport
Hero Member
*****
Offline Offline

Activity: 588
Merit: 500



View Profile WWW
March 31, 2015, 01:02:13 PM
 #130

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!

NiceHash.com - Largest Crypto-Mining Marketplace
kano
Legendary
*
Offline Offline

Activity: 2730
Merit: 1103


Linux since 1997 RedHat 4


View Profile
March 31, 2015, 01:42:46 PM
Last edit: March 31, 2015, 02:06:04 PM by kano
 #131

... 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 Roll Eyes ) 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.
...
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)

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
klondike_bar
Legendary
*
Offline Offline

Activity: 1848
Merit: 1001

ASIC Wannabe


View Profile
March 31, 2015, 02:44:09 PM
 #132

My numbers are in fact correct when calculating what you will actually get paid when you compare that to the predicted payout.

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.

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.

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.

24" PCI-E cables with 16AWG wires and stripped ends - great for server PSU mods, best prices https://bitcointalk.org/index.php?topic=563461
No longer a wannabe - now an ASIC owner!
aurel57
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000



View Profile
March 31, 2015, 02:53:53 PM
 #133

My numbers are in fact correct when calculating what you will actually get paid when you compare that to the predicted payout.

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.

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.

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.

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.
NiceHashSupport
Hero Member
*****
Offline Offline

Activity: 588
Merit: 500



View Profile WWW
April 04, 2015, 03:27:44 AM
 #134

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

NiceHash.com - Largest Crypto-Mining Marketplace
aarons6
Legendary
*
Offline Offline

Activity: 1568
Merit: 1006


View Profile
April 05, 2015, 07:39:21 PM
 #135

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

Activity: 56
Merit: 0


View Profile
April 05, 2015, 07:47:47 PM
 #136

if i put #xnsub on my s3s the pool shows up as down.. do they not support 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.

aarons6
Legendary
*
Offline Offline

Activity: 1568
Merit: 1006


View Profile
April 05, 2015, 07:50:32 PM
 #137

if i put #xnsub on my s3s the pool shows up as down.. do they not support 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.



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?
MegaFall
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
April 05, 2015, 07:55:45 PM
 #138

if i put #xnsub on my s3s the pool shows up as down.. do they not support 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.



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?


pretty sure you need a slash between the port number and the # symbol. Other than that no idea why it wouldn't connect. Mine connected without issues.
aarons6
Legendary
*
Offline Offline

Activity: 1568
Merit: 1006


View Profile
April 05, 2015, 08:08:08 PM
 #139

if i put #xnsub on my s3s the pool shows up as down.. do they not support 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.



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?


pretty sure you need a slash between the port number and the # symbol. Other than that no idea why it wouldn't connect. Mine connected without issues.

thanks, all the documentation i saw doesnt have the slash but i put it in and it seems to be working..
the s5 doesnt need it tho.. its working how i pasted.
strange.
aarons6
Legendary
*
Offline Offline

Activity: 1568
Merit: 1006


View Profile
April 05, 2015, 08:17:21 PM
 #140

if i put #xnsub on my s3s the pool shows up as down.. do they not support 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.



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?


pretty sure you need a slash between the port number and the # symbol. Other than that no idea why it wouldn't connect. Mine connected without issues.

nope its not working.. the pool shows alive now, but still a red X on the worker.. oh well.
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 »  All
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!