Thanks Kano, I appreciate what you and CK are doing/have done for bitcoin and will be pointing my measly 1TH at the pool.
Good luck with your new project!
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2248. (Read 5352229 times)
October 07, 2014, 04:53:12 AM
October 07, 2014, 01:48:51 AM
OK, will have that tiny outage (a few seconds only hopefully) in the next few minutes.
I'll delete/repost this post after it's done.
Switchover done.I'll delete/repost this post after it's done.
Due to the actual few seconds outage most miners probably failed over to backup.
Half are already switched back - the rest will probably switch back in a few minutes.
The change (as mentioned) lets you set a minimum diff per worker.
Also: if you mine to an address, it truncates it in the web header if you are logged in.
That will stop the header getting messed up due to the long 'username'.
Usernames have had another restriction added.
You can't create a new one the same as another, ignoring case, and it also strips any leading or trailing white space or '-' when checking.
Edit: up to 120THs ...
Edit: up to 130THs ...
Final Edit: back to 140
October 06, 2014, 11:07:14 AM
FYI, if anyone noticed 
I added a worker diff management page recently.
However, (if you check git) we're working on passing that info from ckdb to ckpool.
Not done yet, but should be ready tomorrow.
Both ckdb and ckpool handle a user set diff already, but it's not completed passing it between them yet.
The web page already updates the worker diff, so if you have made any changes there, it has stored them, but they haven't been passed to ckpool.
Not until the next change is done tomorrow (it's 3am here)
Also note that when I push the change up to the pool it will require a ckpool restart as well as a ckdb restart, since I made a change in the protocol between the two to handle adding the extra diff information.
So it will be a short delay of up to 5 seconds from restarting them both, to being able to reconnect.
I'll post here when I do it.
Edit: on another note - looks like we're just about to hit 150THs - pity I had to turn off my X3 - coz it was getting too hot here - otherwise we would be over 150 already.
Hopefully be over 150 shortly anyway
I added a worker diff management page recently.However, (if you check git) we're working on passing that info from ckdb to ckpool.
Not done yet, but should be ready tomorrow.
Both ckdb and ckpool handle a user set diff already, but it's not completed passing it between them yet.
The web page already updates the worker diff, so if you have made any changes there, it has stored them, but they haven't been passed to ckpool.
Not until the next change is done tomorrow (it's 3am here)
Also note that when I push the change up to the pool it will require a ckpool restart as well as a ckdb restart, since I made a change in the protocol between the two to handle adding the extra diff information.
So it will be a short delay of up to 5 seconds from restarting them both, to being able to reconnect.
I'll post here when I do it.
Edit: on another note - looks like we're just about to hit 150THs - pity I had to turn off my X3 - coz it was getting too hot here - otherwise we would be over 150 already.
Hopefully be over 150 shortly anyway
October 05, 2014, 10:06:40 PM
Haha, thats all good, my mining is now only affected by the fact that I only have 300GH to throw at the pool, and now theres Multiple people throwing bulk TH at it, so my projected payout it taking a smashing.. that said my chance of actually getting a payout is of course increasing 
October 05, 2014, 09:26:42 PM
October 05, 2014, 09:16:24 PM
oi Kano, what'd ya break ! 
Edit: I got a "This website is down" for a minute there
I did a ckdb update earlier (50 minutes ago)Edit: I got a "This website is down" for a minute there
During that there is a short time frame when the web gets no stats while ckdb reloads.
(Edit: looks like that wasn't the reason by your message timestamp)
Mining and validation works fine - the pool itself doesn't stop or get affected by it other than not allowing new users who aren't currently mining to connect for about 5 seconds.
As per design, this allows ckdb and the web to be changed/updated with no effect at all on the users mining.
ckpool itself also uses an advanced restart option where the miners simply see a reconnect to the pool and no down time if ckpool is restarted with a new version.
Edit2: I'll look into it - seems it might be php not always being happy talking to the linux socket (on rare occasions getting an unhandled error)
Of course it wont affect your mining at all
October 05, 2014, 07:44:55 AM
Spread the word ! http://miningonmyown.com/2014/10/05/great-new-sha256-mining-pools/
October 05, 2014, 07:34:22 AM
oi Kano, what'd ya break !
Edit: I got a "This website is down" for a minute there
Edit: I got a "This website is down" for a minute there
October 05, 2014, 07:31:29 AM
So ckolivas is now working on pool software. This is so interesting. I'll be watching this project to see where it goes. Kolivas has some so much for the community already, I'm sure this project is going to be promising as well.
https://bitcointalksearch.org/topic/ckpool-open-source-poolproxypassthroughredirectorlibrary-in-c-for-linux-790323 
October 05, 2014, 06:58:45 AM
So ckolivas is now working on pool software. This is so interesting. I'll be watching this project to see where it goes. Kolivas has some so much for the community already, I'm sure this project is going to be promising as well.
Not working on, made.
M
October 05, 2014, 06:45:30 AM
Yup, info on it is in the CKPool thread in Software section 
October 05, 2014, 06:42:25 AM
So ckolivas is now working on pool software. This is so interesting. I'll be watching this project to see where it goes. Kolivas has some so much for the community already, I'm sure this project is going to be promising as well.
October 05, 2014, 06:39:32 AM
Yup, everyones making me feel small now lol.. second lowest !
Edit: Lowest! Other guy has 0.00 GH right now !
Edit: Lowest! Other guy has 0.00 GH right now !
October 05, 2014, 06:24:27 AM
New high point at the moment > 140TH
October 04, 2014, 07:03:35 PM
Might point some hashrate at this to test
Once it gets up to 1 PH/s or so a second then blocks will start occurring on a more regular basis. That will probably cause more people to come and push it up even higher. (Myself included.)
M
October 04, 2014, 06:48:53 PM
Might point some hashrate at this to test
October 04, 2014, 07:19:04 AM
Just shy of 50TH now, running smooth!
Edit: 56TH. . on the up and up
Yep rising over the last hour since the restart.Edit: 56TH. . on the up and up
I also made a change to display only the 5min pool average in the top left coz while the pool is small, that number being more dynamic seems appropriate.
Before it would display the 5min pool average for the first hour after a pool restart, them drop to the 1hr pool average after that.
That seemed to cause a little confusion, so I've made it always show the 5min pool average.
October 04, 2014, 06:59:38 AM
Just shy of 50TH now, running smooth!
Edit: 56TH. . on the up and up
Edit: 56TH. . on the up and up
October 04, 2014, 05:56:04 AM
hehe just noticed that, my poor antminer had a heart attack
October 04, 2014, 05:43:15 AM
Server had a hiccup 
- at least it wasn't ckpool/software or anything like that.
I of course have something monitoring it and it's back up already.
It was down for about 10 minutes - half of that was waiting for bitcoind to restart.
(the other half was working out what happened and why it wasn't online)
All good again.
- at least it wasn't ckpool/software or anything like that.I of course have something monitoring it and it's back up already.
It was down for about 10 minutes - half of that was waiting for bitcoind to restart.
(the other half was working out what happened and why it wasn't online)
All good again.
Jump to: