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

[NomadGroup]

Well ... this way you get them faster ... ...
I mentioned before that I'll continue it while it keeps working ... i.e. the payouts contine to be confirmed faster

Cool! Thanks Kano!  Sure works for me!

[kano]

100 blocks left until SegWit locks in! https://xbt.eu

Hmm ... well ... segwit is already locked in
BIP91 did that.

If you happen to have twitter (no I don't and never will) get them to fix the pool name if you can.
It's KanoPool (it says it there in the coinbase so they shouldn't require any verification ...)
At least you see the cat there also
Blocktrail doesn't show the UTF-8 symbols, btc.com does though.

[usernamehere]

100 blocks left until SegWit locks in! https://xbt.eu

Hmm ... well ... segwit is already locked in
BIP91 did that.

If you happen to have twitter (no I don't and never will) get them to fix the pool name if you can.
It's KanoPool (it says it there in the coinbase so they shouldn't require any verification ...)
At least you see the cat there also
Blocktrail doesn't show the UTF-8 symbols, btc.com does though.

I reached out to him on twitter to change it.

[kano]

100 blocks left until SegWit locks in! https://xbt.eu

Hmm ... well ... segwit is already locked in
BIP91 did that.

If you happen to have twitter (no I don't and never will) get them to fix the pool name if you can.
It's KanoPool (it says it there in the coinbase so they shouldn't require any verification ...)
At least you see the cat there also
Blocktrail doesn't show the UTF-8 symbols, btc.com does though.

I reached out to him on twitter to change it.

Thanks!

[kano]

Block! by jotun

[philipma1957]

Block! by jotun

nice  we need to keep them coming


Monthly Statistics

UTC Month.........Pool Avg,,,,,,,Blocks.........Expected.......Mean Diff%,,,,,,,,MeanTx%.......Luck%.....PPS%
2017 Aug........…79.80PHs,,,,,,14..............16.26,,,,,,,,,,,,116.12%...........105.42%........86.12%....89.97%


 we have to get  three by the end of the day to be ahead for the month

[kano]

There'll be a pool restart at 12:00 UTC in half an hour.

It will mean a failover and an immediate failback for ALL miners.

This is an update of the mining pool code to include segwit transactions in our work (since they clearly have been working on the network for a while now) and a fix for the deadlock long ago back in Feb
I've also added a log dump of the block information so I can find out what these valid 'inconclusive' blocks we are getting are.

Unfortunately the update failed dismally
I switched back to the old code again and all is OK again.

Total outage was 2 minutes.
I terminated the pool at 21:59:56, but then had to switch back to the old code, all nodes had reconnected by 22:01:51 so miners would have failed back from then.

More work to do.

[clgrissom3]

Block! by jotun

Nice Job!  This is our 3rd of BLOCK TUESDAY!

[MEARK]

There'll be a pool restart at 12:00 UTC in half an hour.

It will mean a failover and an immediate failback for ALL miners.

This is an update of the mining pool code to include segwit transactions in our work (since they clearly have been working on the network for a while now) and a fix for the deadlock long ago back in Feb
I've also added a log dump of the block information so I can find out what these valid 'inconclusive' blocks we are getting are.

Unfortunately the update failed dismally
I switched back to the old code again and all is OK again.

Total outage was 2 minutes.
I terminated the pool at 21:59:56, but then had to switch back to the old code, all nodes had reconnected by 22:01:51 so miners would have failed back from then.

More work to do.

Good luck Kano and thanks for all that you do! 

[voodooman]

Updating suckz 

Hope you'll find the faulty codesnipped soon!

Is there a posting somewhere out here where you explain how the pool is build up?
Which programming language, which hardware you use etc...?
No details about the code or hardware but maybe some infos about.

I don't wanna build up a pool but i'm coding every now and than some stuff.
So I'm a bit curious bout all this pool stuff. 

You're doing a great job kano! I like the pool you build!
Your avarage working time seems to be nearly 24/7/356 ...RESPECT! 
Don't waste your time with morons trying to annoy you. 
I think you have to do much more important stuff.

Mine ON guys.

[kano]

The mining code is ckpool.
For this update I've just done a few changes as mentioned above (and rolled forward to the current ckpool git ... that failed)

Seems the node code can't handle a pool version update It may need a complete restart of everything.
I'll do some node<->pool testing and work out what's up with that - I was more concerned about block code, and I tested that thoroughly - didn't expect a network protocol problem.
Weird, coz some of the nodes are current code also. As I said ... more work to do

Everything else is my KanoDB
That's the name for the updated closed source version - so no one has any wrong ideas about who wrote almost all of it
The CKDB in the public ckpool git (that I got thrown out of) works fine for a single pool and can handle a few hundred PH - but has no support at all.

A few pools use it: Ver's bitcoin.com did (no idea if they still do) BitClub does, so does LinuxJounal
There's 1 other I know of but I wont mention their names since:
 they removed my copyright off the web site and replaced it with their own copyright ... scumbags

Mine on

[bronder]

So with the hashing power lost that went over to bitcoin cash, it means that in average for the network it should be taking a bit more time to mine those 12.5 bitcoins until a network difficulty update comes over. So the flow of new bitcoin will be slowed down until network diff adjustment, right?

[oawan]

So with the hashing power lost that went over to bitcoin cash, it means that in average for the network it should be taking a bit more time to mine those 12.5 bitcoins until a network difficulty update comes over. So the flow of new bitcoin will be slowed down until network diff adjustment, right?

It looks like not very much went over to bitcoin cash and even more than that amount has been brought online in the last 2 weeks as there is still an expected diff increase of 8.12% in 17 hours.

[clgrissom3]

So with the hashing power lost that went over to bitcoin cash, it means that in average for the network it should be taking a bit more time to mine those 12.5 bitcoins until a network difficulty update comes over. So the flow of new bitcoin will be slowed down until network diff adjustment, right?

It looks like not very much went over to bitcoin cash and even more than that amount has been brought online in the last 2 weeks as there is still an expected diff increase of 8.12% in 17 hours.

That is what I'm seeing as well...it is less than 9 minutes a block average right now so it is faster than the 10 minutes expected.

[tbonetony]

So with the hashing power lost that went over to bitcoin cash, it means that in average for the network it should be taking a bit more time to mine those 12.5 bitcoins until a network difficulty update comes over. So the flow of new bitcoin will be slowed down until network diff adjustment, right?

It looks like not very much went over to bitcoin cash and even more than that amount has been brought online in the last 2 weeks as there is still an expected diff increase of 8.12% in 17 hours.

Well, we still have BTM powerhouse continue pumping out S9 machines. The appreciation of btc will also revive more previously unprofitable older rigs.

[clgrissom3]

Block danbel79! 

This is our 1st of BLOCK WEDNESDAY!

[kano]

Block danbel79! 

This is our 1st of BLOCK WEDNESDAY!

... and 2 payouts, we got the $2.84 back
Just over 1BTC fees also, on a 39 second network block, so not too shabby

[firetreeactual]

[icon73]

So with the hashing power lost that went over to bitcoin cash, it means that in average for the network it should be taking a bit more time to mine those 12.5 bitcoins until a network difficulty update comes over. So the flow of new bitcoin will be slowed down until network diff adjustment, right?

It looks like not very much went over to bitcoin cash and even more than that amount has been brought online in the last 2 weeks as there is still an expected diff increase of 8.12% in 17 hours.

Well, we still have BTM powerhouse continue pumping out S9 machines. The appreciation of btc will also revive more previously unprofitable older rigs.

At the colo I am in we were finally seeing the s7s powering down and with the price up they stopped turning them off.  Right now BCH is about half as profitable as BTC but with the difficulty increases and the fact that the BCH difficulty is going down we may begin to see some more hash moving.

[kano]

So with the hashing power lost that went over to bitcoin cash, it means that in average for the network it should be taking a bit more time to mine those 12.5 bitcoins until a network difficulty update comes over. So the flow of new bitcoin will be slowed down until network diff adjustment, right?

It looks like not very much went over to bitcoin cash and even more than that amount has been brought online in the last 2 weeks as there is still an expected diff increase of 8.12% in 17 hours.

Well, we still have BTM powerhouse continue pumping out S9 machines. The appreciation of btc will also revive more previously unprofitable older rigs.

At the colo I am in we were finally seeing the s7s powering down and with the price up they stopped turning them off.  Right now BCH is about half as profitable as BTC but with the difficulty increases and the fact that the BCH difficulty is going down we may begin to see some more hash moving.

Lulz - no at the moment it makes no sense.
Why mine a pump-and-dump altcoin when you are going to get less than if you were mining BTC.
I'd not expect that to change in the near future either, but saying ... it may be better in the future ... means: yeah good to know - but it's worse now
I know one sizeable miner on there that's apparently only there for "a publicity stunt"

The whole point of BitCH was to avoid the issue of the minority groups trying to force the miners to do something.
The miners all decided to go with BIP91 and that ended it.
BitCH was, however, an obvious way to make some money by those who had the idea in the first place, so they still went ahead after the "supposed" reason why it was going to exist no longer existed.

Meanwhile, whoever the retard was who coded the changes for BitCH, unbelievable how stupid he was.
He clearly had no idea about the fact that people run Bitcoin wallets, duh! and Bitcoin will exist for way longer than that scam.
His wallet screws up or overrides the Bitcoin wallet by default, and uses all the Bitcoin ports, folders and even the same node list lookup.
This all means that they're using the place on the internet (and on your computer) that Bitcoin uses and causing issues doing so.
Every altcoin knows not to use the Bitcoin settings/ports and channels ... except for this retard.

Seeing these things every so often:

Code:

2017-08-08 03:04:43.937070 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader:
 000000000000000000639be19a0123a1c99d9fef89f0b8ac055a77f4ef86ae3b, bad-diffbits, incorrect proof of work (code 16)                                   
2017-08-08 17:07:42.223812 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader:
 000000000000000000639be19a0123a1c99d9fef89f0b8ac055a77f4ef86ae3b, bad-diffbits, incorrect proof of work (code 16)                                   
2017-08-08 19:50:25.006636 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader:
 000000000000000000639be19a0123a1c99d9fef89f0b8ac055a77f4ef86ae3b, bad-diffbits, incorrect proof of work (code 16)                                   

i.e. someone running a BitCH node connecting to a Bitcoin node ... duh how stupid is that ... and the cause is that the guy who coded it didn't bother to use their own ports.
I guess it required him to know what he was doing and spend 30 seconds changing them