Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2054. (Read 5352086 times)

legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
a power failure has caused all s3 with latest update to fail to restart???
Only thing I can think of is if the /overlay/ got corrupted due to the power failure and now there's a problem starting.
But my update makes no difference to that problem.

What do you mean by "fail to restart"
Does it boot and you can see the web but cgminer wont start?
Does it not boot at all?

I power off my S3s every day with the power switch on my PSU and then switch them on again the same way - never had one of them fail to start up when doing that.
S3s show web ui but will not mine at any b/u pool or primary had to do a system reset back to bitmain
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
it happens to me at least twice today.
miners appear with a hashrate like if the pool have a restart.

...
There's been a few restarts dealing with the block change times on that crappy slow getblocktemplate command that some phailure wrote that's in bitcoind ...
...
Last thing we want is an orphan, and this has been to do with keeping our block change time as low as possible.
member
Activity: 97
Merit: 13
it happens to me at least twice today.
miners appear with a hashrate like if the pool have a restart.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
a power failure has caused all s3 with latest update to fail to restart???
Only thing I can think of is if the /overlay/ got corrupted due to the power failure and now there's a problem starting.
But my update makes no difference to that problem.

What do you mean by "fail to restart"
Does it boot and you can see the web but cgminer wont start?
Does it not boot at all?

I power off my S3s every day with the power switch on my PSU and then switch them on again the same way - never had one of them fail to start up when doing that.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
My best share reset a little bit ago.  The pool doesn't say it found a block.  Did the pool restart?
There's been a few restarts dealing with the block change times on that crappy slow getblocktemplate command that some phailure wrote that's in bitcoind ...

... but bestshare isn't an attribute of kano.is ...

It's on solo.ckpool.org and yes someone found a block there earlier.
legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
a power failure has caused all s3 with latest update to fail to restart???
sr. member
Activity: 419
Merit: 250
I'm not rooting for less hash power, I am rooting for more Luck. Luck is one of those things that everyone knows cannot be changed, yet everyone tries to change it. By wearing the same socks every time they play a game, or not shaving, carrying a rabbits foot, etc. The pools luck lately has been better with a lower hashrate. I know and so does everyone else that it makes more sense to have more hashrate, but I was just pointing out that when everyone was letting their beard grow we had good luck...  Cheesy

Just coincidence, yes.  Personally, I would rather the luck/variance roll past quicker.  If bad luck must happen (and it must) I would rather get past it quickly than wait more than a week for a block.  Thus, I prefer a higher hash rate.

The only time I get nervous about high pool hash rate is when a lot of it is rented hash.  I'm going to qualify this by saying that I see no evidence of what I'm about to mention happening in the real world (our long term luck says that it isn't).  That said, rented hash does come with the possibility of reducing luck since the actual rig owner no longer has a stake in the pool payout (only the renter does).  Using the West/NiceHash as an example (only because I'm most familiar with them - not because of anything specific to them), the rig owner selling hash to West/Nice has no incentive to actually submit block solves since they are being paid PPS.  They could withhold block solving shares without penalty.  In fact, they have incentive to not submit solves since it helps keeps difficulty lower and indirectly their PPS rate higher!  The renter, who has the actual stake in the pool, has no way of knowing a block was withheld and pays for the broken hash.  It is a risk that has kept me away from renting hash every time I've considered it.

So, there is one real possible way that higher hash rate could be a bad thing, but as far as I know I've never seen it in action.


Quote
2. Bad luck lasts longer
Another reason that makes us mis-judge mining luck is that when we mine, we mostly experience bad luck. In fact if you go to the trouble of working it out, your hours of mining will be about one-quarter good luck and three quarters bad luck. Why? Bad luck takes longer, good luck rounds take much less time.

3. Assessing luck over time instead of blocks
Another mistake made by novice miners is to assume that the extremes of luck will be the same for all pool over any time frame. This is wrong for two related reasons:

    The more blocks are solved the closer luck approaches 100%
    Because the timeframe for luck to to approach 100% varies depending on number of blocks solved, comparing various pools' luck over the same time period is invalid. Instead we need to compare luck over similar number of blocks.

from: http://organofcorti.blogspot.com/2015/07/faq-bitcoin-mining-and-luck-statistic.html
legendary
Activity: 3583
Merit: 1094
Think for yourself
My best share reset a little bit ago.  The pool doesn't say it found a block.  Did the pool restart?
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Thanks for the continued work you're doing on the S3, kano!
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Payout 364542 sent
340b75b3471ab5c8941fefa121df5cf148f92a102f0ec0bb683a21aa5973ef1a
and confirmed (took 14 minutes)
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
I've put yet another updated AntS3 update archive in my binaries git hub of latest 4.9.2 cgminer.
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

It's another (minor) update to the previous AntS3 release I did:

Code:
2015-Jul-10 Update cgminer-ants3-4.9.2-94e04f6-3.tgz
----------------------------------------------------
Add a table of miner hardware settings to the bottom of the Miner Status page

Tested and running on my pool of course Smiley

If you are already running the 2015-Jul-7 version (the previous update)
Code:
If you update from the 2015-Jul-7 version to the 2015-Jul-10 version,
instead of 'sync' and 'reboot' at the end of the update,
you can instead run this command on your AntS3:
 rm /tmp/luci-modulecache/*
Then the update is complete and nothing else needs to be done.
legendary
Activity: 1274
Merit: 1000
Decided to point my usb sticks here, getting bored this summer with no btc coming in from mining.  Seeing as my usb sticks run all the time and they aren't going to solve a solo block realistically, may as well trickle some Satoshi into the wallet.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Payout 364506 sent
03f85936dce3cc2835870ea3d68e16f8fe5c1b92975d42576d45930667b07723
and confirmed in under 10 minutes Smiley
hero member
Activity: 777
Merit: 1003
not sure how you are calculating the daily TH avg.
i have just over 1T (S5) on this pool and my actual payout numbers are lower then yours.

It is a rough number based on the average pool hashrate between found blocks. Which also means that it assumes that the hashrate has remained constant during the 500%, which never really happens. Sometimes the number I show will be higher, sometimes lower.
legendary
Activity: 1736
Merit: 1006
I am going to de-activating a bunch of accounts on ckpoolmonitor.zachmonroe.com that have been in-active for more than a month. Anyone can go into their account settings and re-activate if they wish. Just trying to lessen the load and speed up processing time. No point in calling the api results for people that are not using it.

not sure how you are calculating the daily TH avg.
i have just over 1T (S5) on this pool and my actual payout numbers are lower then yours.
hero member
Activity: 777
Merit: 1003
I am going to de-activating a bunch of accounts on ckpoolmonitor.zachmonroe.com that have been in-active for more than a month. Anyone can go into their account settings and re-activate if they wish. Just trying to lessen the load and speed up processing time. No point in calling the api results for people that are not using it.
sr. member
Activity: 305
Merit: 250

Thanks for pointing this out... I've been wondering about this for a while now and I missed that thread somehow.
legendary
Activity: 1484
Merit: 1004
I do understand but why do I get low avg for the last 2 blocks since I was there 100% of the block ?

PPLNS doesn't care if you were there 100% of the block, it pays out based on share submissions over a specific time period (or in most cases, specific number of pool-wide share submissions).  The payout range on this pool is 5x network difficulty.  So your average speed over the last 247 billion share submissions (5x network difficulty) was 2.6 Th/s, because you probably have only been mining for the last ~150 billion shares (as of the last rewarded block).

FYI:  If you were to stop mining *right now*, you'd continue to get paid for your previous share submissions until 247 billion new shares have been submitted to the pool by the other users, even if 30 blocks are found before that happened.  You have a period of time required to build up your percentage of the last N shares which you were/are in.  Similarly if you stop mining, you still have a percentage of shares left in the Last N shares for a period of time.  Don't fall into the misconception that PPLNS is short-changing you when you first start.  It builds up your reward slowly, but it has a symmetrical period where you continue getting paid after stopping, the result being it doesn't matter what your mining patterns are, the expected payment for each share submission is never penalized/increased based on prior/future activity.

Good thanks you Eleuthria for the clarification!  Grin
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
That said, rented hash does come with the possibility of reducing luck since the actual rig owner no longer has a stake in the pool payout (only the renter does).  Using the West/NiceHash as an example (only because I'm most familiar with them - not because of anything specific to them), the rig owner selling hash to West/Nice has no incentive to actually submit block solves since they are being paid PPS.  They could withhold block solving shares without penalty.  In fact, they have incentive to not submit solves since it helps keeps difficulty lower and indirectly their PPS rate higher!  The renter, who has the actual stake in the pool, has no way of knowing a block was withheld and pays for the broken hash.  It is a risk that has kept me away from renting hash every time I've considered it.
You have described a risk that is inherent in any rental system, and one I have written about previously.  The owner of the gear has no incentive whatsoever to actually solve blocks.  He's getting paid as long as the hash rate he's providing is consistent with expectations.  For example, on MRR, the rig owner sets a price per GH/s of hashing power, and if you decide to rent his gear, you pay the set price.  As long as that gear performs well (basically over 90% of advertised rates), the rig owner receives the payment (minus MRR fees).  Why should the gear owner care if you solve blocks?  He's been paid, so it doesn't matter.

Now, as a rig owner, and one who rents his gear out on MRR, I have every incentive to actually have my gear using proper mining software (my S3s are all updated with kano's latest cgminer 4.9.2).  Why?  Because when my gear isn't rented, it's pointed towards my own p2pool node, or to ck.'s solo pool.  I absolutely want to be able to solve a block Smiley.
Jump to: