KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2436 blocks

[suchmoon]

Was getting worried approaching 100%

It's getting ridiculous... 96.907% and 12 in a row below 100% (is this the longest streak yet?).

Yes, I've jinxed it now. Brace yourselves for a long one.

They had a streak of 17 green blocks back in Nov 2014.

You're right, blocks 7-23.

I think I started mining on this pool around that time but probably towards the end of that streak because I remember going a week without a block but not the quick ones

Nice to see it growing to 9+ PH/s.

[1714992219]

1714992219

[1714992219]

1714992219

[1714992219]

1714992219

[1714992219]

1714992219

[1714992219]

1714992219

[firetreeactual]

I'm on this pool because of Kano and CK, and because, so far, I'm finding I'm making almost double the BTC per block award as I was at Slush's Pool (sorry 'bout that, ck...). I don't even look at "luck." I feel it's probably because my little 3Th/s means more here, despite our heavy hitters as on any pool, because I'm contributing a higher percentage to the overall effort. That's pretty simple for me to grasp, and to explain to my "silent" (not so much sometimes  ) partner. I enjoy it because there's a reasonable quality of interaction here. Of course I scan and dump a lot, but this is where the learning happens (outside of tearing apart blades). As we used to say on starting a patrol...keep the shiny side up.

[Dkong13]

Just joined this pool last week and compared to slush's pool im averaging 2-3 times what i was getting per block on there with my s5 , plus the fact i seen kano posting on here alot just get a better feel from here well happy i moved over .

[PPOC]

Just joined this pool last week and compared to slush's pool im averaging 2-3 times what i was getting per block on there with my s5 , plus the fact i seen kano posting on here alot just get a better feel from here well happy i moved over .

Glad to hear it, now go get 10PH of your Slush friends to join you so they to can experience the best pool on the network!

[thedreamer]

Just joined this pool last week and compared to slush's pool im averaging 2-3 times what i was getting per block on there with my s5 , plus the fact i seen kano posting on here alot just get a better feel from here well happy i moved over .

Same here. I like the support they offer on the pool as well as the great pay rates. It has grown 3x-4x+ since I started but I like it.

ps... Fly boy eh?

[Mikestang]

Was getting worried approaching 100%

It's getting ridiculous... 96.907% and 12 in a row below 100% (is this the longest streak yet?).

Yes, I've jinxed it now. Brace yourselves for a long one.

They had a streak of 17 green blocks back in Nov 2014.

I think this streak is more impressive given the difficulty level today vs. end of 2014.  What was the pool hash rate back then?  I suppose we could compare pool hash rate then to now vs. network difficulty then to now and see which streak is "better".

Or we could just keep solving green blocks and render my wondering moot. 

[suchmoon]

Was getting worried approaching 100%

It's getting ridiculous... 96.907% and 12 in a row below 100% (is this the longest streak yet?).

Yes, I've jinxed it now. Brace yourselves for a long one.

They had a streak of 17 green blocks back in Nov 2014.

I think this streak is more impressive given the difficulty level today vs. end of 2014.  What was the pool hash rate back then?  I suppose we could compare pool hash rate then to now vs. network difficulty then to now and see which streak is "better".

Or we could just keep solving green blocks and render my wondering moot. 

Based on block 11 it looks like the hashrate would have been ~1 PH/s

[kano]

Since I have mined since the start of the pool, I have a reward in every block.
Thus I also have the Pool hash rate shown for every (valid) block on the Rewards page
Comma separated, lf (not crlf)
Block,Block UTC,Miner Reward,N Diff,N Range,Pool N Avg
http://kano.is/kblocks.txt

[firetreeactual]

Since I have mined since the start of the pool, I have a reward in every block.
Thus I also have the Pool hash rate shown for every (valid) block on the Rewards page
Comma separated, lf (not crlf)
Block,Block UTC,Miner Reward,N Diff,N Range,Pool N Avg
http://kano.is/kblocks.txt

...shazam...    I somehow knew that could be coming...

[Mikestang]

Since I have mined since the start of the pool, I have a reward in every block.
Thus I also have the Pool hash rate shown for every (valid) block on the Rewards page
Comma separated, lf (not crlf)
Block,Block UTC,Miner Reward,N Diff,N Range,Pool N Avg
http://kano.is/kblocks.txt

Awesome, so the pool hash rate at block 23 was 1.31PH.  As I type this the pool hash rate is 9.9PH, 7.56 times larger.
The network difficulty at block 23 was 39,603,666,252. As I type this the network difficulty is 113,354,299,801, 2.86 times larger.

Is there a non-linear increase in how hard it is to find a share higher than value X?  If not, then it looks like the first streak was much more impressive.

[thedreamer]

Why bother? I'm sure most ppl don't care for past random ratios.
 

[kano]

I see what's going you here. You people are trying to get me to do math.

Well even I cheated
I just copy pasted my Rewards page rather than writing some code/sql to generate it for them all

[dmwardjr]

Hi Kano,

Was that our first "automated" payment?

[VRobb]

Since I have mined since the start of the pool, I have a reward in every block.
Thus I also have the Pool hash rate shown for every (valid) block on the Rewards page
Comma separated, lf (not crlf)
Block,Block UTC,Miner Reward,N Diff,N Range,Pool N Avg
http://kano.is/kblocks.txt

Awesome, so the pool hash rate at block 23 was 1.31PH.  As I type this the pool hash rate is 9.9PH, 7.56 times larger.
The network difficulty at block 23 was 39,603,666,252. As I type this the network difficulty is 113,354,299,801, 2.86 times larger.

Is there a non-linear increase in how hard it is to find a share higher than value X?  If not, then it looks like the first streak was much more impressive.

It would appear to be linear, as far as my studies of all this is leading me.  Fascinating all this!

[fr4nkthetank]

Your thinking of the 5Nd the wrong way.
I am going to see if I can come up with a better way to explain this to people...

Edit: Maybe this will help?

     Current difficulty = 113354299801

     That means that 1Nd = 113354299801

     5Nd = 113354299801 x 5 = 566771499005

     That means that when a block is found the last 566771499005 shares are paid.

     So for every one of those 566771499005 shares that you submitted you are paid for.
     You are paid for the ratio of your shares to the 566771499005 that are paid.

     The 5Nd is not a time, but a number of shares...

I'm a completely noob about technical knowledge of the bitcoin protocol, but now i understand this 5Nd thing thanks to you.
Really helpful explanation.

Kano should put this on the website, under his explanation.  its a good "practical example".

[kano]

Hi Kano,

Was that our first "automated" payment?

Heh, no, there never will be completely "automated" payments.

The first (very simple) change I made a few weeks ago was being able to process them before they confirm.
So usually there's only a few minutes delay (unless I'm asleep) between +101 and sending the payout since I set it up (randomly) in advance.

The changes the other day were to do with how I get the actual payout data from the server.
I simplified that process greatly and secured it a little more also.

These steps do of course lead to the next one: one payout per day, but that may still be a week or more before I get to working on that.

[kano]

... and on the subject of changes ...

There's been some important changes on the ckpool local <->remote node code by -ck so there'll be a set of updates with those in about 18 hours.
I'll post again tomorrow morning (it's early afternoon here now) an hour before I do that with ckpool on all the nodes.

Before that, I'm now going to do a ckdb restart in about 20 minutes.
Will happen shortly after the next shift completes and is processed.
... and the usual reminder about a ckdb restart, no miners are affected by it at all.
Only the web site stats are unavailable.

This is a small update to support a small change in ckpool, to provide me with some more useful data about connections and I'll enable it on the workers page with a minor web change a bit later also.

[dmwardjr]

Thank you for the updates.  Much appreciated.

I remember now when you mentioned "once a day."

That payment was so fast after the 101 confirmations, I just assumed it was "automated."   

[kano]

...
Before that, I'm now going to do a ckdb restart in about 20 minutes.
Will happen shortly after the next shift completes and is processed.
... and the usual reminder about a ckdb restart, no miners are affected by it at all.
Only the web site stats are unavailable.

This is a small update to support a small change in ckpool, to provide me with some more useful data about connections and I'll enable it on the workers page with a minor web change a bit later also.

CKDB Restart completed.
Took a little over 9 minutes this time:
[2016-01-14 14:00:59.058+11] Listener received terminate message, terminating ckdb
[2016-01-14 14:10:10.668+11] reload queue completed 0m 13.617s

[firetreeactual]

Everything's spiffy here. All five dwarfs are digging like crazy...no bumps. Mahalo!