KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2436 blocks

[vh]

From the article
http://www.coindesk.com/bitcoin-price-400-network-disruption/

Still, the digital currency experienced sharp gyrations this week amid news that the network was exceeding its capacity for transactions, a development that resulted in users paying sometimes substantially higher fees.


We're seeing a lot of delays lately.  If block size isn't increase to handle more transactions, it will just come at a cost of higher fees to handle the traffic via prioritizations. Of course I have the option to increase the fees, but I never had to do that before to get it across within 2hrs or less.  Dont think just as a miner as we love higher fees for fatter blocks but think of the overall bitcoin market investments.  If you're running a business, the delay and sometimes rejection due to delays can have a huge impact on your business, making you think twice about increasing your usage or expanding with bitcoins.  It does have a huge impact on the BTC prices when the network is not efficient on handling the growing traffics.  I guarantee you, as soon as we get a solution agreed upon, BTC prices will sky rocket.  I'm willing to bet the farm on that.  Failure to agree on that solution is what's keeping BTC down.

P.S How many of you guys are seeing delays of 6-12hrs lately?   I'm definitely seeing more and more of that.  Even Nice Hash acknowledge that as well as many other companies.

back to your original pool related question:
https://bitcointalk.org/index.php?topic=789369.msg13566071;topicseen#msg13566071

[nhando]

Thanks for taking the time to pull that for me VH.  That was good reading.  I know this topic's been beaten to death and so is the ROI topic for our hardware but it's 2 of the most important things for us.   Man, it's always so lovely to see Kano pool all green, let's get some more Blocks!!!

[sorry2xs]

Just a thought, remember that does algorithms don't care about roi or anything else it is like spok "Logic" 

[nhando]

Just a thought, remember that does algorithms don't care about roi or anything else it is like spok "Logic" 

Was saying the 2 discussion topics.  This block size and the Antminer S7 ROI topic.

[sorry2xs]

IMO i am not aware of any hardware to date that is capable to of ROI.

[clgrissom3]

Block by pt0x with 262THs...his second on kano!

[nhando]

Block by pt0x with 262THs...his second on kano!

Woot Woot...............Keep it rolling in!!!

[edonkey]

I was worried about a transaction of mine given the recent congestion. But this last Kano block picked it right up.

The previous block that passed me over was fucking empty. Disgusting...

Thank you Kano for running the kind of pool that's good for the community as a whole. We need this pool!

[Biodom]

Alt-coin discussion about to be deleted all above - just so you know in advance ...

here is on topic: kano's pool is great, but bitcoin's endless infighting sucks big time.
if it will continue, btc will be an alt coin in 6-12 mo tops. people understand this, hence discussing what is on their mind, maybe at a wrong place.
I deleted my posts (responses to other posts) myself. Do whatever with this one.

[sorry2xs]

done

[wolfen]

Ready for another block

[nhando]

How much more time before it's Elen's shift?  Let's see if she can get us a block again.

[clgrissom3]

How much more time before it's Elen's shift?  Let's see if she can get us a block again.

She comes up in 10 shifts at about 48 minutes each...less time if we hit any blocks along the way as a block ends the shift.

[nhando]

How much more time before it's Elen's shift?  Let's see if she can get us a block again.

She comes up in 10 shifts at about 48 minutes each...less time if we hit any blocks along the way as a block ends the shift.

That's your lucky charm CLG...............Let's DO it again.  But 480 mins is too long, any other lucky charms earlier?  =)  Hoping for another block before I go to bed.

[thedreamer]

Anyone else still having problems with the difficulty on the pool?

Sometimes, even with a set difficulty, it doesn't want to work.

[kano]

Anyone else still having problems with the difficulty on the pool?

Sometimes, even with a set difficulty, it doesn't want to work.

Define 'work'
I can check the full log to see what it has been for you over the past hours.

Oh and yeah - block - 40mins ago

[kano]

I will be doing a CKDB restart after the start of the next hour - in about 45 minutes - it should be around 20 past the hour.
When the next shift is summarised in the next hour.
No miners will be affected since ckpool isn't affected by this.

This is a bug fix for the new share recording code for checking that miners are submitting properly.
It has nothing to do with miner rewards, just the new code for tracking high diff shares and checking that miners are submitting expected shares.
I'll post again just before I do it and of course also after the restart has completed.

I've delayed the CKDB until the next shift summary after the next hour - again in about 45 minutes.

Seems my guess at the time of this one was way off by about 20minutes - will be some time in the next 5 or 10 minutes.
Thus, the next one will be much closer to the hour, which means a much faster ckdb restart.

CKDB restart in the next minute.

Restart complete ... and a block during the restart!
Yay nhando

Edit: and wow was that close

Code:

[2016-03-06 20:39:06.390+11] BLOCK! ok Diff 100.3% (158941180646/158427203767.4) 

[Ares~]

Anyone else still having problems with the difficulty on the pool?

Sometimes, even with a set difficulty, it doesn't want to work.

Yes my some of my miners appear to been affected by the restarts and diff set high and then the miners shares drop, although my block % seems ok diff seems not right and high, Kano not sure if you can check when you have a moment, worker1 seems to always be affected and now looks like workers 2, 4 and 5 now too, username is Ares on website, can PM me your findings, thanks.

EDIT: 11:14 - Kano, I have manually set diff for worker3 & worker4 but seems to have had no effect.

[wolfen]

I will be doing a CKDB restart after the start of the next hour - in about 45 minutes - it should be around 20 past the hour.
When the next shift is summarised in the next hour.
No miners will be affected since ckpool isn't affected by this.

This is a bug fix for the new share recording code for checking that miners are submitting properly.
It has nothing to do with miner rewards, just the new code for tracking high diff shares and checking that miners are submitting expected shares.
I'll post again just before I do it and of course also after the restart has completed.

I've delayed the CKDB until the next shift summary after the next hour - again in about 45 minutes.

Seems my guess at the time of this one was way off by about 20minutes - will be some time in the next 5 or 10 minutes.
Thus, the next one will be much closer to the hour, which means a much faster ckdb restart.

CKDB restart in the next minute.

Restart complete ... and a block during the restart!
Yay nhando

Edit: and wow was that close

Code:

[2016-03-06 20:39:06.390+11] BLOCK! ok Diff 100.3% (158941180646/158427203767.4) 

Damn,that WAS close! Great job nhando!

[CapnBDL]

Hey Gang,

It is almost decision time for me. Last 4 blocks have had payouts less than 0.001xxxxx for my little farm. Tough choice for me to make, but if I get any smaller, I am considering pointing my hash at the solo pool and hoping for the best. I will hang-out for a few more blocks to see what happens, but it will soon become time for me to try Lady Luck.

Sad days ahead for me.

CapnBDL