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

[dkaufman]

Excellent, nice payout...

+2!

-dave

[-ck]

There will be a short downtime as we update the ckpool code and migrate some data within the pool.

EDIT: Complete

[joesmoe2012]

I'm in with the sibling stuff as well, just let me know when you are ready to launch a few.

[-ck]

Updated the top post to reflect our new best hashrate. Stored for prosperity.

Code:

[2014-10-30 19:53:15] Pool:{"hashrate1m": "666T", "hashrate5m": "667T", "hashrate15m": "665T", "hashrate1hr": "653T", "hashrate6hr": "632T", "hashrate1d": "627T"}

[wttbs]

Updated the top post to reflect our new best hashrate. Stored for prosperity.

Code:

[2014-10-30 19:53:15] Pool:{"hashrate1m": "666T", "hashrate5m": "667T", "hashrate15m": "665T", "hashrate1hr": "653T", "hashrate6hr": "632T", "hashrate1d": "627T"}

6 6 6 the number of the beast 

[DanielRo]

I'm in with 3 of my S3+.

[philipma1957]

Updated the top post to reflect our new best hashrate. Stored for prosperity.

Code:

[2014-10-30 19:53:15] Pool:{"hashrate1m": "666T", "hashrate5m": "667T", "hashrate15m": "665T", "hashrate1hr": "653T", "hashrate6hr": "632T", "hashrate1d": "627T"}

6 6 6 the number of the beast 

please update to 700+

 as you are over 710th

[sgi02]

Updated the top post to reflect our new best hashrate. Stored for prosperity.

Code:

[2014-10-30 19:53:15] Pool:{"hashrate1m": "666T", "hashrate5m": "667T", "hashrate15m": "665T", "hashrate1hr": "653T", "hashrate6hr": "632T", "hashrate1d": "627T"}

6 6 6 the number of the beast 

Official pool of SATAN!! 10/10 would mine again

Happy Halloween to every miner hashing through these ghoulish times

[QuiveringGibbage]

https://blockchain.info/tx/7b47a5415f69a092f5d2c252ff6bc60f34c333e52ef04cdc24adf485f9db270d

Code:

[10:25:54] <kanoi_> blockchain only showing 1 block so that's a good sign :)
[10:26:03] <QG> yoouu pew pew pew!!!

QG

[bgibso01]

Thank you sir, may I have another!

[kano]

... and it confirmed shortly after that - so all good

[techgeeks]

We just found another.

[Axiste]

wicked! BTC

[mdude77]

That's ridiculous.

M

[-ck]

There'll be a little blip in mining as we upgrade the ckpool code. You may see a small burst of rejects and a redirect notice but you probably won't failover during the upgrade due to the way ckpool handles changeover, but if you do it won't last long.

[Cheeseater]

There'll be a little blip in mining as we upgrade the ckpool code. You may see a small burst of rejects and a redirect notice but you probably won't failover during the upgrade due to the way ckpool handles changeover, but if you do it won't last long.

I'm noticing it

[philipma1957]

So I have been mining an s-3 for about 40 of the 80  hours it took to make the block.

So we wait for payouts about 10 hours?

[-ck]

Sorry, full restart took a little longer than planned. Up properly now.

[philipma1957]

Sorry, full restart took a little longer than planned. Up properly now.

seems to be working well.

[-ck]

And a mini bounce for further scalability improvements.

Just so people know what the improvements are, if you check what's gone into the latest ckpool code you'll see changes that correspond with the pool upgrades (doesn't get more open than that does it?).

The ckpool code was not remotely limiting, but being able to see the pool working live and profiling where the CPU is used makes for excellent instant development of whatever is currently the biggest CPU user. The main connection event handler was converted from poll to epoll reducing CPU usage of that to 1/10th and the share processing workqueue was broken up into many threads (proportional to the number of CPUs on the machine) to better distribute out share processing. We're now prepared for about 10x as many workers as we were yesterday, so keep em coming...