Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2211. (Read 5352067 times)
December 22, 2014, 01:55:21 AM
I believe I was over paid. I have had connection issues this past 3 days so was not expecting much.
December 21, 2014, 08:46:56 PM
Woot...Lightsword is kicking some serious ass today!
Yep the collection of farms is doing well!Lets hope they stay and don't run away again
Bug still not found - but doing the payout shortly for 335151 - then will get back to tracking down the problem.
If anyone has any issues with their current payout address (they shouldn't
I have a few checks I do of the payout addresses each payout) let me know via PM or IRCUnfortunately the bug takes out ckdb - so until I can find and fix it, the address change is still unavailable.
Was in the related section of code where I wasn't looking, coz only 1 person has access to that web menu (percent payouts) and it caused the other menu to lock up, only after it was accessed.
ckdb is reloading - all will be back to normal in ~10minutes.
I've committed a change that will show the reload work queue size in the bottom left of the footer.
When ckdb completes it's reload, it then works though all the queued work that arrived from ckpool while the reload was running.
This can get above 500k messages (last one was 599156)
So anyone looking at the web site will be able to see - in the footer - how out of sync it is.
It's not enabled yet, but will be next time I need to restart ckdb - thus also you'll be able to see when the queue after the reload has cleared and know the stats on the web site have caught up to current.
December 21, 2014, 04:07:04 PM
Woot...Lightsword is kicking some serious ass today!
December 21, 2014, 10:14:09 AM
Had the web/ckdb stop working unexpectedly a couple of times tonight.
As usual, that's no affect on mining.
I've disabled the payout address change page temporarily while I try to work out if that's the cause or something else.
I'll post again (tomorrow) when I've enabled it again.
Didn't find the cause - took me a while though coz I setup the old server with a complete copy of the pool and tried to make it fail ... but didn't succeed.As usual, that's no affect on mining.
I've disabled the payout address change page temporarily while I try to work out if that's the cause or something else.
I'll post again (tomorrow) when I've enabled it again.
I've re-enabled it just now and hopefully overnight we wont have the same problem again.
There was one other possible cause and that problem was blocked early on when it happened.
Anyway, it's 2am here so I'm unlikely to do the payout until the morning - probably in about 6 or so hours - but I'll try stay awake for a little while to see if anything happens like yesterday now that I've re-enabled the Settings menu.
Failed with the first person trying to set their payout address (mdude77)
I disabled it again and now restarting ckdb so the stats will show lotsa '?' for the next ~10 minutes.
This time I didn't actually remove the web page - so it shows your current address - but I've disabled that one section changing your address.
Well at least it gave me another clue to find the problem.
Yeah.
It clocked for a really long time then I got "website is down". At least the address there is mine.M
December 21, 2014, 10:07:57 AM
Had the web/ckdb stop working unexpectedly a couple of times tonight.
As usual, that's no affect on mining.
I've disabled the payout address change page temporarily while I try to work out if that's the cause or something else.
I'll post again (tomorrow) when I've enabled it again.
Didn't find the cause - took me a while though coz I setup the old server with a complete copy of the pool and tried to make it fail ... but didn't succeed.As usual, that's no affect on mining.
I've disabled the payout address change page temporarily while I try to work out if that's the cause or something else.
I'll post again (tomorrow) when I've enabled it again.
I've re-enabled it just now and hopefully overnight we wont have the same problem again.
There was one other possible cause and that problem was blocked early on when it happened.
Anyway, it's 2am here so I'm unlikely to do the payout until the morning - probably in about 6 or so hours - but I'll try stay awake for a little while to see if anything happens like yesterday now that I've re-enabled the Settings menu.
Failed with the first person trying to set their payout address (mdude77)
I disabled it again and now restarting ckdb so the stats will show lotsa '?' for the next ~10 minutes.
This time I didn't actually remove the web page - so it shows your current address - but I've disabled that one section changing your address.
Well at least it gave me another clue to find the problem.
December 21, 2014, 06:55:50 AM
December 21, 2014, 06:31:48 AM
Another win for Lightsword!!!!! You feelin' it 
I know I am December 20, 2014, 06:52:19 PM
This latestst block will have to reach 100 confirms before it gets paid, I'm sure you will be able to fix the addy before that happens.
December 20, 2014, 06:49:49 PM
Top post of this page..."payout address change is temporarily disabled", it'll be back soon.
Then I guess I'll find out what I set it to when I get paid.
At least it could be shown.
M
December 20, 2014, 06:47:04 PM
Top post of this page..."payout address change is temporarily disabled", it'll be back soon.
December 20, 2014, 06:31:33 PM
Another win for Lightsword!!!!! You feelin' it
Wow, that's a lot of hash.
That said, first time ever I've been in the top 10 hashers for a pool.
That said ... I'm not seeing how to set my payout address? The one I see on the link to blockchain.info doesn't seem to be one of my addresses?
M
December 20, 2014, 05:50:13 PM
Another win for Lightsword!!!!! You feelin' it
December 20, 2014, 10:01:28 AM
Had the web/ckdb stop working unexpectedly a couple of times tonight.
As usual, that's no affect on mining.
I've disabled the payout address change page temporarily while I try to work out if that's the cause or something else.
I'll post again (tomorrow) when I've enabled it again.
As usual, that's no affect on mining.
I've disabled the payout address change page temporarily while I try to work out if that's the cause or something else.
I'll post again (tomorrow) when I've enabled it again.
December 20, 2014, 01:19:51 AM
334947 payout sent - using the correct payout range - the last 2 blocks (~188%)
This payout range will of course keep increasing until it reaches 500% and from then on will the N will be the last 500% for each block found.
Oh and the payout just confirmed also
This payout range will of course keep increasing until it reaches 500% and from then on will the N will be the last 500% for each block found.
Oh and the payout just confirmed also
December 19, 2014, 05:34:39 PM
Anyone paying close attention to the pool
Restarted ckdb earlier so when I do the payout later I've fixed the 5N count back limit (restart had no effect on mining of course)
(anyone curious: https://bitbucket.org/ckolivas/ckpool/commits/7470af8c4624c30bae5eb2629250fac5f14d1665 )
Also then did a ckpool restart a few minutes ago that would have only shown up as a reconnect in cgminer - to increase the linux file limits so the large worker counts you probably noticed on the web site (> 22k) had a lot more room (old limit was 64k, new limit is 512k)
Restarted ckdb earlier so when I do the payout later I've fixed the 5N count back limit (restart had no effect on mining of course)
(anyone curious: https://bitbucket.org/ckolivas/ckpool/commits/7470af8c4624c30bae5eb2629250fac5f14d1665 )
Also then did a ckpool restart a few minutes ago that would have only shown up as a reconnect in cgminer - to increase the linux file limits so the large worker counts you probably noticed on the web site (> 22k) had a lot more room (old limit was 64k, new limit is 512k)
December 19, 2014, 08:54:23 AM
I bet having the network diff rate change recently throws a bit of a curve in the math.
December 19, 2014, 08:20:01 AM
Heh - was doing a ckdb update ... and while ckdb was down/restarting we found a block
Waiting on the confirm
Edit: confirmed
So in case anyone didn't really follow all my rambling on about now using 5N Waiting on the confirm
Edit: confirmed
This means that the full new block (~125%) shares will be paid out in this payout
But it stops at 125% due to the limitation imposed by the current markersummaries
(according to what I said here: https://bitcointalksearch.org/topic/m.9855962 )
Oh well - I'll fix that before the payout
December 19, 2014, 06:51:05 AM
Sorry Kano, my question was still in regards to the particular block height referenced above.
Con's answered that blockchain.info screws up sometimes.
It gets it wrong.
That block has no transactions, thus the coinbase reward is only 25 BTC.
December 19, 2014, 06:21:09 AM
Sorry Kano, my question was still in regards to the particular block height referenced above.
December 19, 2014, 06:11:25 AM
So the pool was awarded and received 25BTC empty block at this height? Sorry, I've spent most of my time up till now learning more about the hardware and operating it. Now I'm trying to get into the nuts and bolts of the rest.
All blocks are awarded (currently) 25BTCThen on top of that they get any unused BTC in each transaction confirmed in the block - commonly called a transaction fee.
i.e. someone makes a transaction to move 1.234 BTC to another address, but they put 1.2339 BTC in the target address, that imbalance, 0.0001 BTC gets added onto the block reward
... and FYI the block reward halves every 210000 blocks ... which at 10 mins per block is very close to 4 years ... but as with the last year of commonly faster than 10 mins per block, it will probably be a little less than 4 years to the next halving.
The last halving was Nov 2013
Jump to: