common kano work your magic were at 21 hours and no blocks found
I finally decided to move my farm over from antpool to kano and apparently I stepped into a 23 hour test of patience.
Ok so seriously I have pushed antpool on my youtube channel but as antpool keeps growing the logic to support the smaller pools makes more sense. That being said we all still need to make money so if I am in, I would like to share this with my subscribers. However, for me to use what little influence I have right now can someone maybe give me an higher level overview of how a ckpool works vs say a larger pool like antpool. I read the thread on ckpool last night and it was a bit over my head. I am trying to learn more of the of the inter workings.
Thanks in advance for your help!
https://www.youtube.com/channel/UCwoLtAoTpf1e6pRqpwNI54A?view_as=public Heh -ck beat me to it, but anyway, here's my TL;DR; version
Well some important points, in no particular order, are:
1) We never mine empty blocks if transactions are available (so far never made an empty block)
2) We've averaged the highest block sizes of all pools: Solo first, Kano.is second.
http://data.bitcoinity.org/bitcoin/blocksize/30d?t=lScroll down to "Blocks size by mining pool" and click on "Average size" twice
3) CKPool is written in C and -ck is a linux kernel developer who clearly knows about writing performance critical code.
(the software used in most miners mining BTC is cgminer, the performance/management code written almost entirely by -ck)
4) CKPool and CKDB are two separate parts of the pool that makes sure that the mining and reporting are separate and somewhat independent
This means that the priorities of the two parts of the pool are met separately and do not conflict with each other.
5) We have VERY low orphan rates due to how fast the code runs and how well we've setup our block distribution
6) We run custom bitcoind, optimised for performance, no blacklisting, no bitcoin fungibility issues - all based on core with performance increases.
7) We know what we are doing from the ground up, it's not a point and click pool running someone else's software, we wrote all the code and maintain it ourselves
8 ) The code running on the pool is open source, there for anyone to read and use:
https://bitbucket.org/ckolivas/ckpool/src9) The BTC in the pool is there all in the open for anyone to see where it goes. Each block, after it's confirmed, is paid directly to the miners, and the last address on each payout is the leftover dust, or payments for accounts that don't have an address. All easy to track and see where everything is going.
9) We understand bitcoin from the ground up.
10) You wont find me making posts that aren't backed by facts, or if I do make a mistake, I will certainly correct my errors if I discover that, or someone points it out. I'm not always right and I have no issue realising that fact.
So now that you've hit a 310%+ block just when you've joined, it's time for me to post a table that shows what to expect from any pool regarding block% and luck:
0.39346934028737 50.000% 1 in 1.6
0.63212055882856 100.000% 1 in 2.7
0.77686983985157 150.000% 1 in 4.5
0.86466471676339 200.000% 1 in 7.4
0.95021293163214 300.000% 1 in 20.1
0.98168436111127 400.000% 1 in 54.6
0.99326205300091 500.000% 1 in 148.4
0.99752124782333 600.000% 1 in 403.4
0.99872735771441 666.666% 1 in 785.8
0.99908811803445 700.000% 1 in 1096.6
0.99966453737210 800.000% 1 in 2981.0
0.99987659019591 900.000% 1 in 8103.1
0.95539904465973 311.000% 1 in 22.4
So yep, 1 in 22.4 blocks is EXPECTED, on average, to be greater than 311%, where we currently are.
There's no way to control the % of each single block we find, there's expected results, and we clearly do find blocks within those expected results as the table at the top of the blocks page shows
https://kano.is/index.php?k=blocksThank You Kano, this is exactly what I was looking for. If you don't mind my referencing any part of this in the future when I put a video out on your pool that would be great.