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

[kano]

Block! By chapi2016, salud!

That was probably an S7

[1714138298]

1714138298

[1714138298]

1714138298

[1714138298]

1714138298

[fvineyard]

Another block and with a decent fee too!

Nice!

[clgrissom3]

Block! By chapi2016, salud!

Good job Chapi2016!  Welcome to the Acclaim Board with your 1st Kano block!  I think our expected daily block count is now ~1.25 per day so we need to hit another to bump us over!

[NomadGroup]

Block! By chapi2016, salud!

Good job Chapi2016!  Welcome to the Acclaim Board with your 1st Kano block!  I think our expected daily block count is now ~1.25 per day so we need to hit another to bump us over!

There goes another!  Hehe

[kano]

Block! By chapi2016, salud!

Good job Chapi2016!  Welcome to the Acclaim Board with your 1st Kano block!  I think our expected daily block count is now ~1.25 per day so we need to hit another to bump us over!

There goes another!  Hehe

Canaan with an A7v2

[kano]

Woo!
Another by Canaan 2 blocks later

[NomadGroup]

Woo!
Another by Canaan 2 blocks later

Woooow!  That's 4 today by my time!  Awesome!!!

[will]

Code:

./cgminer --quota "1;stratum+tcp://stratum.kano.is:3333" -u wvr.0 -p x --quota "1;stratum+tcp://solo.ckpool.org:3333" -u myaddr.wvr -p x 

Rifts are sad events and they suck. Hard.

kano, it's understandable for ck to not use ckdb as he's mentioned that the db stuff is beyond his remit. As a result he has a dependency on you to test that commits don't introduce retroactive bugs in ckdb. You're really the best person for that as you run it in production and are the only person doing so openly. If you're using an old version of it (August 2016), the private fork happened then, not now.

Re: the private CDF calcs: I can digg that it very much classifies as secret-sauce for a pool. If a pool is a government, defense materiel would definitely include custom, unshared BWH-protection and/or luck-based pool operator actions. Warnings that lead to bans and eventual non-payment is serious shit and affects your reputation as a solid pool operator. So you have to protect that.

As someone who's been working on wrapping my head around the whole segwit thing (the tech, et al aspects of it) I can say that you have both been invaluable inputs on providing unfettered-, independently- and well-formed opinions on what will be a big change for bitcoin. Or not. Your polar opposite views on the whole thing is an example of what bitcoin is: people arguing until they're pissed at one another and eventually coming up with something that works for both of them. It's a good thing. This situation is not all that different.

Disagreements are important. In any venture: When two men always agree, one of them is unnecessary. The work you both do is as inter-dependent as it is important.

https://www.youtube.com/watch?v=JYc05gZFly0

W

[kano]

kano, it's understandable for ck to not use ckdb as he's mentioned that the db stuff is beyond his remit. As a result he has a dependency on you to test that commits don't introduce retroactive bugs in ckdb. You're really the best person for that as you run it in production and are the only person doing so openly. If you're using an old version of it (August 2016), the private fork happened then, not now.

ck's been recently making changes to ckpool for ckdb, for the Bitmain guy, coz he paid him to do them, that brake the ckdb payouts.
I hardly see "beyond his remit" in that.

I am not the only one who runs ckdb in production, others do.
It was 2 other people, BitClub and RogerVer, who had ckdb startup crashes when they updated with ckpool changes that were for ckpool - but they were changes that affected ckdb also.
Normally if you change a library function that requires new rules about calling it, you'd change all code that calls it, not ignore the ckdb code  that calls it and was broken by the change.

As for when the fork happened - who cares.
He has 2 forks of ckpool.
I created one and he commented positively about it when I said I created it.
Then the other day he got pissed at me responding to his jibe at me in similar fashion, then locked me out of everything saying it was coz of my fork. Oddly that included locking me out of cgminer and taking away all my privs in the IRC channels.
Nothing to do with code or forks, he was just throwing a tantrum coz of what I replied pretty much similar to what he said to me.

You feel the need to lecture me for -ck
I'll respond.

P.S. this is over, finished end of story. Not sure why you felt the need to bring it up again.
As is CKDB as per his words after he locked me out:
"< conman> leaving all the others depending on ckdb in the lurch yay \o/"

... The work you both do is as inter-dependent as it is important.

He certainly doesn't agree with you.

Re: the private CDF calcs: I can digg that it very much classifies as secret-sauce for a pool. If a pool is a government, defense materiel would definitely include custom, unshared BWH-protection and/or luck-based pool operator actions. Warnings that lead to bans and eventual non-payment is serious shit and affects your reputation as a solid pool operator. So you have to protect that.

Nothing to do with private CDF calcs.
Some of the current testing is there in the public git and the database and code changes for the stats are all there also.
There's ways a miner can make it very hard to detect their withholding.
This new testing is doing something very different to detect that, and I will be able to check things retroactively with some effort later - since I always keep all data.

[bit2255]

Perhaps it's me and I need to apologies to you guys.

I've been mining on the pool since Thursday and we've only found 2 blocks, prior to me pointing my miners at the pool it looked like things were travelling along quite nicely.

I am sooo glad you are taking the blame.

I started Tuesday and I thought I was the reason why 

Even though I (we) are off to a slow start, from what I can tell and read, I am glad I chose this pool.

I am also going to double my Th/s in a about 2 days, when my 2nd R4 arrives..now I am a double sized small home (newbie) miner!

It's all good guys!  Hopefully we'll be back on track soon.  Although I'm starting to have my doubts after the diff jump!  .  Let's hope that when your second R4 arrives it brings us back some green luck!

Well, got my 2nd R4 today and its up and running (although a little hot!). So that means a shorter wait for the next block  and guaranteed green luck!!!!

Time for me to take credit ...lol

Seriously..WooHoo three at a time!! Nice job

[will]

You feel the need to lecture me for -ck

I speak for nobody except myself, apologies if the rhetoric of my words implied otherwise.

[kano]

You feel the need to lecture me for -ck

I speak for nobody except myself, apologies if the rhetoric of my words implied otherwise.

Rhetoric seems quite obvious

... he's mentioned that the db stuff is beyond his remit. As a result he has a dependency on you to test that commits don't introduce retroactive bugs in ckdb.

[clgrissom3]

Woo!
Another by Canaan 2 blocks later

It's great to wake up to 3 blocks in the tank!  That's what I'm talking about!

[thepixelgeek]

Awesome!

I just added my two R4's yesterday morning.

[clgrissom3]

Block by wetsuit!  This is his 3rd Kano block and our 4th of the day!  

[VRobb]

Block by wetsuit!  This is his 3rd Kano block and our 4th of the day!  

Surf's up!! Blockmania continues! 

[firetreeactual]

Back to work! Yowza...

[kano]

Block by wetsuit!  This is his 3rd Kano block and our 4th of the day!  

Surf's up!! Blockmania continues! 

S9v2

[miner0007]

Everyone you are welcome!
You may thank me for joining and bringing luck to the pool by sending me 0.001 btc each.

[bit2255]

Hey..that was my line...

We are rocking!!