I think this bad luck come after kano change the payout method?
I remember the payment could be include in any block from any pool but now the payout is only goes through kano pool after it has 100 confirmation and kano pool find a block.
Just some noob opinion.
or maybe just like everyone else say it is from rental.
ignore me if it has nothing to do with the payout method but from what I see, this pool luck start changing after that payout method change.
maybe worth investigating.
No |
|
|
|
I'm sure the limit of the pool is well into the double ph digits, so nobody should worry. Lol
Probably quadruple.  1000+ PH? Doubt that. If you have a spare EH to throw at the pool I'd be happy to let you try. |
|
|
|
I'm sure the limit of the pool is well into the double ph digits, so nobody should worry. Lol
Probably quadruple. |
|
|
|
Short big rentals, aka shocking the pool, rarely works imo. Also MRR seems 'safer' to rent from. I think something (either some bad rigs/bwithholding or latency issues)on the other rental service has much more reduced chances to get a solve.
No amount of hashrate would shock this pool. It's a term used when adding a large rental that is many times more than normal rates. Nothing to do with the pool's ability to handle it or not. I'm quite aware, but it was an opportunity to remind people nonetheless. |
|
|
|
Short big rentals, aka shocking the pool, rarely works imo. Also MRR seems 'safer' to rent from. I think something (either some bad rigs/bwithholding or latency issues)on the other rental service has much more reduced chances to get a solve.
No amount of hashrate would shock this pool. |
|
|
|
The pattern to luck vs hash can be demonstrated quite clearly by this simple analysis... This may be the smartest post I've seen on this association yet. Good work. |
|
|
|
I hope everyone remember this massive luck we are getting today and keep it in mind when we have bad luck.
No. I demand Kano investigate the cause of this massive luck streak as there must be something wrong in the code or China must be doing something bad or DDoSing themselves or backdooring bitcoin for us or someone's siphoning blocks and channeling them into our pool or they're doing a block withhold resubmit unattack or something. |
|
|
|
It looks like most of the recents blocks are found thanks to big rentals !
Luck is no match for raw hashrate. |
|
|
|
[2016-05-14 08:53:20.709] Possible block solve diff 276641025652.444397 !
[2016-05-14 08:53:21.033] BLOCK ACCEPTED!
[2016-05-14 08:53:21.034] Solved and confirmed block 411709 by 17wigaWBYC7vjpahbRa6bKMCYPSjfPYHFb
[2016-05-14 08:53:21.034] User 17wigaWBYC7vjpahbRa6bKMCYPSjfPYHFb:{"hashrate1m": "831T", "hashrate5m": "559T", "hashrate1hr": "112T", "hashrate1d": "5.41T", "hashrate7d": "25T"}
[2016-05-14 08:53:21.034] Worker 17wigaWBYC7vjpahbRa6bKMCYPSjfPYHFb:{"hashrate1m": "831T", "hashrate5m": "559T", "hashrate1hr": "112T", "hashrate1d": "5.41T", "hashrate7d": "25T"}
[2016-05-14 03:53:22.623] Block solved after 9603795290 shares at 4.9% diff
De block and confirmed kano ckpool block too! |
|
|
|
[2016-05-13 23:37:15.481] Possible block solve diff 210094493929.545868 !
[2016-05-13 23:37:15.615] BLOCK ACCEPTED!
[2016-05-13 23:37:15.615] Solved and confirmed block 411682 by 1Ng6d13H1A3PYi9E8knZqsgn8ubNXhmmzk
[2016-05-13 23:37:15.615] User 1Ng6d13H1A3PYi9E8knZqsgn8ubNXhmmzk:{"hashrate1m": "1.66P", "hashrate5m": "1.78P", "hashrate1hr": "958T", "hashrate1d": "148T", "hashrate7d": "82.8T"}
[2016-05-13 23:37:15.615] Worker 1Ng6d13H1A3PYi9E8knZqsgn8ubNXhmmzk:{"hashrate1m": "1.66P", "hashrate5m": "1.78P", "hashrate1hr": "958T", "hashrate1d": "148T", "hashrate7d": "82.8T"}
[2016-05-13 23:37:15.615] Block solved after 222641670542 shares at 114.6% diff
|
|
|
|
Huh? Does not compute. Lol
In a nutshell, ignore it. |
|
|
|
Hi. Any insight why the 2 do not match? I thought bestshare should match whomever has the highest one at the current round?
Probably just an oversight in the code to not reset some users for some reason. Certainly not harmful. Not sure it's a reset issue as I watched it change yesterday after switching my stuff to this pool. So its not a bestshare from the last solved block. Ah well if you were not a miner till after the block changed, then it's a very old entry from a previous pool restart potentially. |
|
|
|
Hi. Any insight why the 2 do not match? I thought bestshare should match whomever has the highest one at the current round?
Probably just an oversight in the code to not reset some users for some reason. Certainly not harmful. |
|
|
|
|
Completely and utterly irrelevant to bitcoin mining, so no. Moving thread to where it might be relevant.
|
|
|
|
Question.
In the pool stats it gives a best-share of :5,457,984,292
My pool stats show a bestshare of : 96,813,886,812.256165
??
Best share resets after someone finds a block. Bestever doesn't reset. |
|
|
|
|
Absolutely no computer of any size shape cost or form can produce bitcoin in any meaningful capacity whatsoever any more. Even the most powerful supercomputer is useless. You need dedicated ASIC bitcoin mining hardware to mine bitcoins. The computers don't do the mining, they just run the mining hardware.
|
|
|
|
|
Show Posts
