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

Hi Kano, are you doing some more changes/updates? I noticed the web say "Database is updating, mining is ok" or something along those lines. And now the stats are back to ?

I was going to post I feel a block coming along soon, as I saw the hash rate spike....

Thanks Kano, I'll not get so disheartened then if things take a bit longer.  

For anyone using the CKPool stats app on android, it looks like the app still crashes when the kano.is website stats are not available. This was meant to be fixed in the last update but possibly something still amiss. I've sent feedback to the app developer.

200% is when I start thinking about curses.

As I've mentioned before, if it was sooner than that I'd go nuts.
Blocks are expected, on average, to be longer than 200% 1 in ~7.4 blocks so yeah that's pretty common even at 200%

And I thought I had put a curse on the block streak by not having chicken last night.

Gonna do another ckdb update shortly.
(I was waiting for a block so as not to annoy anyone waiting also)
No miners will be affected at all as usual for a ckdb restart.
Just a small 'fix' update for the lock checking changes I added the other day.
Web site will have lotsa '?' for the next 15mins or so.

Edit: restart completed about 5min ago

Yes, seems like a basic fundamental principal to all this used electricity as well...  
If not block isn't accepted..   That would make short work of this practice.
I mean, is the goal to create something real or just play a game here?

Yeah I didn't notice that one in the console late last night
Here it is:

It had to be > 99% to trigger an "Unworthy" share

That's the first share since the start of Nov that was within 105% of being a block
- that's when I added the code in ckdb to, independently to ckpool, report the "within 105% or better" shares
(that includes stale shares/blocks as well)

Edit: heh I forgot, I set it to 5%

So close yet so far. And will feel a hell of a lot further in 10(ish) days with these diff + increases 

"bestshare": 77859525012.565674} with 12th! 

It seems to me like there should be some code in the bitcoin network itself with logic than can have a rough idea of the number/size of outstanding transactions and then require blocks to contain a certain number/size/percentage-of-total-block-size of outstanding tx.  I agree that it's a fundamental issue.

Certain pools have been mining empty blocks for a long time (cough Eligius cough)
Other pools mine empty blocks and SPV mine (cought f2pool, antpool, ?? cough)

The excuse given is that mining an empty block just on a block change, is faster than putting transactions into it.
Of course it is.

BUT our nice kano.is ckpool pool does block changes usually faster than cough Eligius cough anyway.
The argument given by these 'others' to mine empty blocks was based on poorly written software and blaming transactions, rather than fixing their own software.

YES solo.ckpool.org and kano.is would blow the sox off every pool on the planet in block change times if we did SPV and Empty block mining.

NO I'm not going to do that even though I could. I don't see the excuse of gaining a few 100 milliseconds in block change time appropriate for risking major network forks with SPV. I don't see the need to reduce the number of transactions confirmed by a few % as neceessary since we already beat the empty block (non SPV) pools.

YES we already average better than all the non SPV pools ... ... ... ... and solo often beats some of the SPV pools ... ... ... ...

(yeah I should get around to updating kano.is to the solo block change code soon - it's now been more than long enough for me to not be concerned about reliability)

It's because of their crap pool software.  There's nothing in the protocol that disallows block creation with no transactions other than the coinbase one... so it's not a flaw in the bitcoin ecosystem.

Why is this allowed?  I thought the whole point in mining was to process transactions.  Is the system that broken?

So what is this post all about? Antpool DDOS and blacklist Kano pool?

https://np.reddit.com/r/btc/comments/3vixef/f2pool_just_threatened_to_ddos_and_blacklist_kano/

Cool, now that this is solved - can we go back eating chicken? 

It can't be him. He's 44 years old and last I checked I was 45.

Character and honor seems to be in short supply with those guys these days so I suppose anything is possible.  That is why I came over to the Kano side…

They claim to be under ddos - but which pool wasn't under ddos the last couple of months? So would be really wondering if they will blame kano for this.

Nothing on the radar here so far.