Payout 396360 sent (1.5hrs ago)
820857f0e59cf4e19f4937368351244f862b5c2af1e0dd939341e9567a680c9b
and confirmed
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1763. (Read 5352295 times)
February 03, 2016, 07:43:10 AM
February 03, 2016, 06:35:34 AM
Right, and guess what, for 20 minutes (during the ckdb restart) he got no data ... meanwhile the pool was fine.
so it is just a reporting glitch, thank you.
My apologies for misunderstanding the situation
February 03, 2016, 05:46:55 AM
No idea what that is, but mining was OK for everyone non-stop except the remote nodes for 20 minutes.
Look at the pool graph, that shows the hash rate NOT zero.
it is from https://ckpoolmonitor.zachmonroe.com/
February 03, 2016, 05:46:01 AM
No idea what that is, but mining was OK for everyone non-stop except the remote nodes for 20 minutes.
Look at the pool graph, that shows the hash rate NOT zero.
it is from https://ckpoolmonitor.zachmonroe.com/
February 03, 2016, 05:35:26 AM
Will be some rolling updates of ckdb and ckpool urgently now.
ckdb first, no miners will be effected.
This will be done as soon as the sena block shift is created (it was just created as I was typing this, so restart will be in a couple of minutes)
Then shortly after it will be a ckpool restart.
Sorry for the short notice but ram is becoming an issue again, so I need to push the ckdb restart.
I was working on some new ckdb code but it's not ready yet, so will have to do this now rather than wait.
All done.ckdb first, no miners will be effected.
This will be done as soon as the sena block shift is created (it was just created as I was typing this, so restart will be in a couple of minutes)
Then shortly after it will be a ckpool restart.
Sorry for the short notice but ram is becoming an issue again, so I need to push the ckdb restart.
I was working on some new ckdb code but it's not ready yet, so will have to do this now rather than wait.
Ouch :p
Look at the pool graph, that shows the hash rate NOT zero.
February 03, 2016, 05:32:41 AM
Everything fixed and back up.
The remote nodes where offline, but the main node was OK, so hopefully everyone had a failover back to the main node.
The remote nodes where offline, but the main node was OK, so hopefully everyone had a failover back to the main node.
February 03, 2016, 05:30:25 AM
Will be some rolling updates of ckdb and ckpool urgently now.
ckdb first, no miners will be effected.
This will be done as soon as the sena block shift is created (it was just created as I was typing this, so restart will be in a couple of minutes)
Then shortly after it will be a ckpool restart.
Sorry for the short notice but ram is becoming an issue again, so I need to push the ckdb restart.
I was working on some new ckdb code but it's not ready yet, so will have to do this now rather than wait.
All done.ckdb first, no miners will be effected.
This will be done as soon as the sena block shift is created (it was just created as I was typing this, so restart will be in a couple of minutes)
Then shortly after it will be a ckpool restart.
Sorry for the short notice but ram is becoming an issue again, so I need to push the ckdb restart.
I was working on some new ckdb code but it's not ready yet, so will have to do this now rather than wait.
Ouch :p
February 03, 2016, 05:07:23 AM
Bit of a problem with ckpool at the moment, I've just shut down all remote nodes DE, SG, JP
I'll let everyone know when it's sorted and they are back online.
The main mining node is OK
I'll let everyone know when it's sorted and they are back online.
The main mining node is OK
February 03, 2016, 04:45:20 AM
Will be some rolling updates of ckdb and ckpool urgently now.
ckdb first, no miners will be effected.
This will be done as soon as the sena block shift is created (it was just created as I was typing this, so restart will be in a couple of minutes)
Then shortly after it will be a ckpool restart.
Sorry for the short notice but ram is becoming an issue again, so I need to push the ckdb restart.
I was working on some new ckdb code but it's not ready yet, so will have to do this now rather than wait.
All done. ckdb first, no miners will be effected.
This will be done as soon as the sena block shift is created (it was just created as I was typing this, so restart will be in a couple of minutes)
Then shortly after it will be a ckpool restart.
Sorry for the short notice but ram is becoming an issue again, so I need to push the ckdb restart.
I was working on some new ckdb code but it's not ready yet, so will have to do this now rather than wait.
February 03, 2016, 04:38:09 AM
494 396446 canaan.3333 25.53477937 2016-02-03 09:08:27+00 +5 Confirms 161,186,183,636 134.285% 0.739 1
February 03, 2016, 04:34:10 AM
Question about confirmations. At the time of writing this 396446 block shows three confirmations, but there are only two blocks mined after block 396446. So how can there be three confirmations?
Because someone decided that when a block is found it's called "1 confirmation"True, it confirms each transaction for the first time, but that's the odd naming used for blocks also.
Ok.
February 03, 2016, 04:23:39 AM
Will be some rolling updates of ckdb and ckpool urgently now.
ckdb first, no miners will be effected.
This will be done as soon as the sena block shift is created (it was just created as I was typing this, so restart will be in a couple of minutes)
Then shortly after it will be a ckpool restart.
Sorry for the short notice but ram is becoming an issue again, so I need to push the ckdb restart.
I was working on some new ckdb code but it's not ready yet, so will have to do this now rather than wait.
ckdb first, no miners will be effected.
This will be done as soon as the sena block shift is created (it was just created as I was typing this, so restart will be in a couple of minutes)
Then shortly after it will be a ckpool restart.
Sorry for the short notice but ram is becoming an issue again, so I need to push the ckdb restart.
I was working on some new ckdb code but it's not ready yet, so will have to do this now rather than wait.
February 03, 2016, 04:20:23 AM
Is this normal for the invalid/stales? How would one reduce it or is that normal usage? Any advice? Thanks.
http://oi67.tinypic.com/xmkbo3.jpg
Yeah that's on the high side, but it depends on your miner quality and ping distance to the node you are mining at.http://oi67.tinypic.com/xmkbo3.jpg
Also see above post.
Looking over some of my miners i noticed that the block % seemed to have a greater dependence on valid /invalid then hashing rate. or was that an optical illusion? lol
I was researching a odd reading from an S4 (was getting 2.4 with stock PSU) Looking more I found that when setting Voltage I accidentally deleted the 7 0725 under voltage I and apparently other then high 1.5 invalid Stale nothing else was showing up bad.
http://i68.tinypic.com/smg2mo.jpg
http://i66.tinypic.com/24uzqzr.jpg
Strangest thing is other then the stale reject rate being high everything else looked ok,,,,, so far that is.
But when i corrected it my invalids only dropped to .90 I thought i was on to something I guess its back to the drawing board if anyone could point me in a good direction I would be very thankful
PS
I looked again and some were over 25% stale and almost started yelling at the till i realised BLOOOOOOOOCKKKK . someone do the chicken dance lol
February 03, 2016, 04:16:46 AM
Question about confirmations. At the time of writing this 396446 block shows three confirmations, but there are only two blocks mined after block 396446. So how can there be three confirmations?
Because someone decided that when a block is found it's called "1 confirmation"True, it confirms each transaction for the first time, but that's the odd naming used for blocks also.
February 03, 2016, 04:14:24 AM
Question about confirmations. At the time of writing this 396446 block shows three confirmations, but there are only two blocks mined after block 396446. So how can there be three confirmations?
February 03, 2016, 03:47:08 AM
Convinced my friend today to come over to kano.is
Wasn't hard after telling about SVP mining
although I don't know if it still exists. But got him to come over!
Wasn't hard after telling about SVP mining
although I don't know if it still exists. But got him to come over! 
February 03, 2016, 03:27:34 AM
I'm moving in. Since I started, I never solve a block yet. Hope I do here 
I should be at full throttle in a few hours.
I should be at full throttle in a few hours.
I've solved a block 48h after joining this pool, in fact it was my first block EVER since I started mining in late December.
I started at around 6B diff ;-)
February 03, 2016, 03:04:02 AM
Thanks zOU, the 0.0001 is what I was looking for
But looking at the cold statshot, that my first block on Kano with 41Gh/s paid Half of what I get for running nearly 2 Th/s now...won't be much longer before the threshold closes in on me
But looking at the cold statshot, that my first block on Kano with 41Gh/s paid Half of what I get for running nearly 2 Th/s now...won't be much longer before the threshold closes in on me
February 03, 2016, 02:59:33 AM
I'm moving in. Since I started, I never solve a block yet. Hope I do here
I should be at full throttle in a few hours.
I should be at full throttle in a few hours.
I've solved a block 48h after joining this pool, in fact it was my first block EVER since I started mining in late December.
February 03, 2016, 02:45:44 AM
FYI, see the payments I got depending on my average Hashrate:
Code:
1.26THs 0.00186176
1.26THs 0.00183406
1.26THs 0.00179136
1.01THs 0.00156424
560.88GHs 0.00093513
484.15GHs 0.00082263
189.31GHs 0.00032145
172.29GHs 0.00029470
144.91GHs 0.00024774
So "roughly", anyone below 0.0001x144.91/0.00024774 = 58Gh/s average /day will only get dust.
that was yesterday.
basically:
How many Ths does the pool need to reach before your 2Ths payout is 0.0001 ?
Ths BTC
2 0.0001
25
Answer: 500000 Ths / 500Phs
Currently your 2Ths gets you 0.0027BTC
Ths BTC
2 0.002761
25
18109.38066 <= calculated pool Hash
Pool hash taken from homepage:
CKPool: 18,107.12THs
so my calculation is roughly good 18.109 Ths calculated vs 18.107 Ths real
with my 1.25Ths, i'll stop getting payment when the pool reaches 312Phs approx.
(as long as a block is 25BTC)
Jump to: