Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 991. (Read 5352429 times)
April 26, 2017, 01:32:53 PM
The last payout I received was for block 463271. Is this correct or am I missing some payouts ?
April 26, 2017, 12:44:03 PM
How much hashing power do you need to get 1 BTC per block?
pool is about 42ph so 4.2 ph would be 1/10 a block is say 13.5 with fees so 4.2 ph or 1/10 gives you 1.35 btc
so 1/1.35 x 4.2ph is your answer roughly 3.11ph . it is more complex to be exact.
first you need to do the 3.11ph for 5n which is maybe 80 hours in a row
second if you add 3.11ph the pool goes from 42 ph to 45.11 ph and you would be short the 1 btc per block
third I used 1 btc for the fees. meaning the block is 13.5 btc some are lower some are higher.
fourth with a bit of in my head math I boost the 3.11ph to 3.333 ph if the pool is at 45th
So for today a range of 3.11 ph to 3.333 ph is a good guess
KanoPool: 43,133.14THs
Shares: 97,211,402,178 (18.67%)
Invalids: 34.1k (0.31%) · 302.1M (0.31%)
Mining Rewards
The rewards you've earned for each block the pool has found.
See the Payments page for the payments you've been sent.
Block----- Block UTC------ Miner Reward---N Diff----- N Range--------- Pool N Avg
463608 26/Apr 15:01 14.19369732 2.630T 79hr 0m 26s 39.72PHs
463502 25/Apr 22:48 12.61703676 2.618T 80hr 38m 43s 38.73PHs
I got my n range from the bold line above it fluxes
I got the pool hash from 39.72 and 38.23 and 43.13 it fluxes
so my estimate is 3.11ph to 3.33 ph
April 26, 2017, 12:37:56 PM
How much hashing power do you need to get 1 BTC per block?
April 26, 2017, 10:08:17 AM
Block by moecarrimNEW! Welcome to the Acclaim Board with your 1st Kano block (even though moecarrim has 5 blocks to his credit)! 
Good fees this one has!
Good fees this one has!
April 25, 2017, 11:28:19 PM
I'm always curious about how this stuff works. I asked about this another time about a low KB block awhile ago and the explanation given was that it was found immediately after another block.
But I see other cases today where blocks were found seconds apart I.E. block 463527/8/9 and they were still able to include ~1000kb worth of transactions and generate ~13.7btc.
And I believe at the time of the block there was still quite a few unconfirmed transactions. Is it set to only include high paying transactions in certain cases or did it not have time to find transactions to include?
But I see other cases today where blocks were found seconds apart I.E. block 463527/8/9 and they were still able to include ~1000kb worth of transactions and generate ~13.7btc.
And I believe at the time of the block there was still quite a few unconfirmed transactions. Is it set to only include high paying transactions in certain cases or did it not have time to find transactions to include?
April 25, 2017, 09:50:33 PM
Just processed the payout for that block and did a check on the reason why it was a pretty low fee block.
It was a 25s network block, so was certainly the reason.
It was a 25s network block, so was certainly the reason.
April 25, 2017, 09:15:04 PM
Way to go, brother...that's why we're here. Stay safe.
E
E
April 25, 2017, 08:24:39 PM
Yeah I was landing at LAX on the runway when we got the block.
It was a definite take-two to have the notification pop up as I reconnected to 4G on the runway ... within a minute or 2 of when we got the block.
Then to wonder why TF ckpool didn't think it was a block worth confirming - it decided it wasn't a valid block for some reason ... but fortunately the NL node was happy with it
I'll have to go thru the bitcoind debug.log later when I get back home ... in aboout 18 hours or so.
I've just manually confirmed the block, but it resets the top stats when I do that, so the display will be off until the next block we find.
The actual block stats get corrected when it's confirmed so it has of course done the payouts correctly and will with the next block - this is one of the reasons why CKDB does this second confirmation of all the stats for blocks and payouts - not based on the '~' estimate, but all done based on the actual correct DB numbers later once it's sure it has all the data in the database.
The top % numbers are from when the block was confirmed (which I just did) and will be corrected by the next block.
It was a definite take-two to have the notification pop up as I reconnected to 4G on the runway ... within a minute or 2 of when we got the block.
Then to wonder why TF ckpool didn't think it was a block worth confirming - it decided it wasn't a valid block for some reason ... but fortunately the NL node was happy with it
I'll have to go thru the bitcoind debug.log later when I get back home ... in aboout 18 hours or so.
I've just manually confirmed the block, but it resets the top stats when I do that, so the display will be off until the next block we find.
The actual block stats get corrected when it's confirmed so it has of course done the payouts correctly and will with the next block - this is one of the reasons why CKDB does this second confirmation of all the stats for blocks and payouts - not based on the '~' estimate, but all done based on the actual correct DB numbers later once it's sure it has all the data in the database.
The top % numbers are from when the block was confirmed (which I just did) and will be corrected by the next block.
Yay, Kano to the rescue!
April 25, 2017, 08:19:22 PM
Yeah I was landing at LAX on the runway when we got the block.
It was a definite take-two to have the notification pop up as I reconnected to 4G on the runway ... within a minute or 2 of when we got the block.
Then to wonder why TF ckpool didn't think it was a block worth confirming - it decided it wasn't a valid block for some reason ... but fortunately the NL node was happy with it
I'll have to go thru the bitcoind debug.log later when I get back home ... in aboout 18 hours or so.
I've just manually confirmed the block, but it resets the top stats when I do that, so the display will be off until the next block we find.
The actual block stats get corrected when it's confirmed so it has of course done the payouts correctly and will with the next block - this is one of the reasons why CKDB does this second confirmation of all the stats for blocks and payouts - not based on the '~' estimate, but all done based on the actual correct DB numbers later once it's sure it has all the data in the database.
The top % numbers are from when the block was confirmed (which I just did) and will be corrected by the next block.
It was a definite take-two to have the notification pop up as I reconnected to 4G on the runway ... within a minute or 2 of when we got the block.
Then to wonder why TF ckpool didn't think it was a block worth confirming - it decided it wasn't a valid block for some reason ... but fortunately the NL node was happy with it
I'll have to go thru the bitcoind debug.log later when I get back home ... in aboout 18 hours or so.
I've just manually confirmed the block, but it resets the top stats when I do that, so the display will be off until the next block we find.
The actual block stats get corrected when it's confirmed so it has of course done the payouts correctly and will with the next block - this is one of the reasons why CKDB does this second confirmation of all the stats for blocks and payouts - not based on the '~' estimate, but all done based on the actual correct DB numbers later once it's sure it has all the data in the database.
The top % numbers are from when the block was confirmed (which I just did) and will be corrected by the next block.
April 25, 2017, 08:05:09 PM
I hope we are not in vain to planet the planet with heat?
What?? I do not comprehend. 
The pool itself is working fine. Odds are the reporting interface is - stuck. The block has been confirmed multiple times so eventually all will be well.
I just moved my gimpy R4 (1 board dead) back from a weeks vacation on -ck's new lottery pool to kano again and it is reporting the normal climb in hash rate.
I'm glad to see that work itself out! Whew!
April 25, 2017, 07:38:37 PM
Personally, I would like to see how that last block shakes out once Kano has had his coffee and gets online. Wonder how the shares will be reset.
EDIT: Especially if we crack another block before the shares reset. Could be interesting.
EDIT: Especially if we crack another block before the shares reset. Could be interesting.
Kano San may be flying over some place in pacific ocean
or he was kidnapped somewherein the state while catching the HASH whales 
Yes, forgot about his state-side travels. He may not be back home yet or be able to get to the pool/database, etc., to fix anything. We shall see.
Ahha,, it's been fixed and the shares have reset!
April 25, 2017, 07:33:34 PM
Personally, I would like to see how that last block shakes out once Kano has had his coffee and gets online. Wonder how the shares will be reset.
EDIT: Especially if we crack another block before the shares reset. Could be interesting.
EDIT: Especially if we crack another block before the shares reset. Could be interesting.
Kano San may be flying over some place in pacific ocean
or he was kidnapped somewherein the state while catching the HASH whales April 25, 2017, 07:20:10 PM
I just moved my gimpy R4 (1 board dead) back from a weeks vacation on -ck's new lottery pool to kano again and it is reporting the normal climb in hash rate.
So that explains the 2-3PH rise in pool hash over the last few hours! LOL
April 25, 2017, 07:02:45 PM
I hope we are not in vain to planet the planet with heat?
What?? I do not comprehend. The pool itself is working fine. Odds are the reporting interface is - stuck. The block has been confirmed multiple times so eventually all will be well.
I just moved my gimpy R4 (1 board dead) back from a weeks vacation on -ck's new lottery pool to kano again and it is reporting the normal climb in hash rate.
April 25, 2017, 06:58:55 PM
Personally, I would like to see how that last block shakes out once Kano has had his coffee and gets online. Wonder how the shares will be reset.
EDIT: Especially if we crack another block before the shares reset. Could be interesting.
EDIT: Especially if we crack another block before the shares reset. Could be interesting.
April 25, 2017, 06:52:48 PM
I hope we are not in vain to planet the planet with heat?
What?? I do not comprehend.
April 25, 2017, 06:39:09 PM
I hope we are not in vain to planet the planet with heat?
What?? I do not comprehend.
April 25, 2017, 06:32:34 PM
I hope we are not in vain to planet the planet with heat?
What?? I do not comprehend.
April 25, 2017, 06:30:43 PM
I hope we are not in vain to planet the planet with heat?
April 25, 2017, 06:24:16 PM
https://blockchain.info/tx/004df284915161edc0c18e21c26534b14ea4af126cc56528a5b544b86891eae9
we got that block we have 4 confirms
we got that block we have 4 confirms
In that case, if the pool DB ends up getting reset get ready for some astonishing *reported* hash rates for a bit when it comes back up
I've seen mine climb over 10x higher for a few min as the reporting system catches up with the pool shares ran. Definitely screen shot material there Jump to: