Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1973. (Read 5352097 times)

Good job guys, finally some good news from mining pools. I hope the hashrate continues to increase at ckpool.

2 blocks in one day!  happy dance!

heh, I refreshed when we had 5 seconds on the last block shown.

That's a pretty quick announcement!

Yay!  F5 worked!  Block!

Let's hope it stays up above the 4PHs!  Recent solid results will probably keep us there!  See who decides to keep joining us!

Can't beat that! 

Payout 387053 sent
ee5d8b2fc72c17885841736df46ee6762a37285cf77136daa367c124866f4a36
and confirmed

YEP ... the force has been strong recently  ... nice to see the 'blocks' screen showing two currently being confirmed at the same time - second time in a week   

... and another to make up for that last one being a little over expected average

Well done andrewhaar with 2.2THs!

Yeah that one's timing was a little on the amusing side

Pool has been over 4PHs most of the day, looking good

Yay block

There's no settings required so you'd have to provide more details to work out what's wrong.
Though, if you misspell your username (case sensitive) or use an invalid mining address then yeah that will cause errors.
As it says on the site:
Registered username or Bitcoin address, followed by a dot '.' or an underscore '_', followed by a worker name.

I was pointing a gecko compact 12gh miner to the site and get a all rejects. The antrouter mines without problems so what am I missing in my bat file to mine your pool



............seems to be a usb or device error on my side so will be all set when I track it down

Still like my S5 just works

And a font size big enough to see without a magnifying glass would be great too

During a ckdb restart the stats won't show for ~15 minutes

During a ckpool restart that will depend on if you failover or manage to reconnect in time.

However it seems there's a bug with the 1hr stat, so if all the others are ok, that would explain it.
The ckpool restart was 10:16:45 UTC (5-Dec)
The ckdb restart was from 09:49:20 UTC (5-Dec) for about 15 minutes

--

Edit:
Payout 386726 sent
4172d6f42e47a820728fa597fdfde2d5967273c0d290be9e5b881f741a44ba8e
and confirmed

Hi Kano, would the server updates you have done cause the ckpool status app to report my hash rate was low? I'm guessing so as the site probably was not available/updating hash rates, but thought I'd ask.

Thanks.

EDIT: It was only earlier today that I got a low hash alert, stats back to normal now.

No, not with anything available on the web site at the moment.

Is there a way to tell how much of my last reward is attributed to a particular worker in my group ?

I will be doing some main server updates shortly.

First will be an update for ckdb.
As usual the 1st ckdb update will not affect miners, but just the web site will be showing not much useful for the ~15 minutes after I restart ckdb.
The changes involved are all behind the scenes.
I've added some new lock checking and (100%) deadlock prediction code to get things ready for threading some of the threads that can block and slow things down on rare occasions.
ckdb + ckpool is fine at 6PH (as we saw yesterday when we found that block) and all probably would be ok well above 40PH, but there's ways I can make sure of that and make that upper limit higher ... so with this change I'll be able to verify all is OK to go ahead and speed ckdb up even more.
I don't expect any problems with the changes even though they are rather extensive:
(as can be seen here: https://bitbucket.org/ckolivas/ckpool/commits/c7f03c2a331f111696f0e8163f295461711e8eb5 )
but of course they don't affect ckpool running so the only side effect could be some restarts of ckdb due to new ckdb code problems - that I don't expect that at all.


After that I'll also do a ckpool restart.
There's some changes in there that may help improve performance also - but ckpool is far from having any performance problems on the pool.
For the majority of users, a ckpool restart should just show as a reconnect in cgminer.
Though some minority of users will see a failover since not everyone reconnects fast enough
- inside the 30 seconds required to avoid a failover in cgminer.

I'll post again once it's all done.

Edit: ckdb restart complete - web site all back ok

Edit2: yeah the 2nd step was done also (about 8 minutes ago) ... now almost back to where we were before that