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

[HerbPean]

Does it seem like the time between blocks is getting longer? On the network in general?

I know look at the average.  I am more curious about a shorter term look.  21 days maybe?

according to the stats on the header of kano.is it shows 23 min between blocks

Not really, quite the opposite hence why the projected diff is going up. If the block generation times were slow then it would be over 10m and trending toward a negative diff, but we are still projected at over 5% increase.


Bitcoin Difficulty:   178,678,307,672
Estimated Next Difficulty:   187,988,569,390 (+5.21%)
Adjust time:   After 1369 Blocks, About 9.3 days
Hashrate(?):   1,262,550,030 GH/s
Block Generation Time(?):   
1 block: 9.8 minutes
3 blocks: 29.5 minutes
6 blocks: 59.0 minutes
Updated:   15:35 (2.1 minutes ago)

The current estimation is off because it's taking in count some data of the past diff. It's more like 1-2% at the moment.

[kano]

Do you think running my iron on a proxy would help to get more blocks?
I have 4 s3's and one s7 running against one now, s7 got 36Gig best share.

A proxy wont make much of a difference unless you have network bandwidth issues and/or lots of miners.

Basically a non-passthru proxy simply means that on a block change, you get one work item from the pool rather than N work items for N miners, the proxy then divides the one work item up into N work items for the miners and transmits the N items locally


Aside: if the proxy is slow or has slow network capabilities then it actually makes it worse, not better, so using a slow crappy device as a proxy isn't the best idea.

[wolfen]

Do you think running my iron on a proxy would help to get more blocks?
I have 4 s3's and one s7 running against one now, s7 got 36Gig best share.

A proxy wont make much of a difference unless you have network bandwidth issues and/or lots of miners.

Basically a non-passthru proxy simply means that on a block change, you get one work item from the pool rather than N work items for N miners, the proxy then divides the one work item up into N work items for the miners and transmits the N items locally


Aside: if the proxy is slow or has slow network capabilities then it actually makes it worse, not better, so using a slow crappy device as a proxy isn't the best idea.

Thanks.
Is 28 s7's a lot of miners? What is a slow proxy machine? I have a acer aspire one running ubuntu 14 I was going to try.

[kano]

Well any i3 equivalent hardware with gigabit ethernet would be fast enough.

Below that, no idea, it would depend on the hardware performance and the number of miners.

[chikenfeed]

think you blocked me kano

[Crispyato]

Time to bust this block...

[kano]

think you blocked me kano

https://bitcointalk.org/index.php?topic=789369.msg14571905#msg14571905

[kano]

Will be doing a CKDB restart after 01:00 UTC - a bit after 01:20 UTC I think it will be.
No miners will be affected.
Web site will show lotsa '?' ... for about 15-20 minutes.

This will be a longer than normal restart to get a lot more logging of the sequence numbers that I'm trying to resolve the issue in the new code.
It will actually be 2 restarts - so about twice as long.

It will be the shift summary after 01:00 UTC which should be a bit after 01:20 UTC

[rkinnin]

Will be doing a CKDB restart after 01:00 UTC - a bit after 01:20 UTC I think it will be.
No miners will be affected.
Web site will show lotsa '?' ... for about 15-20 minutes.

This will be a longer than normal restart to get a lot more logging of the sequence numbers that I'm trying to resolve the issue in the new code.
It will actually be 2 restarts - so about twice as long.

It will be the shift summary after 01:00 UTC which should be a bit after 01:20 UTC

Once again...Kudo's on the notification! 

Very much appreciated.

PS.  Maybe it will kick-start some newly found blocks too.  ;-)

[clgrissom3]

Will be doing a CKDB restart after 01:00 UTC - a bit after 01:20 UTC I think it will be.
No miners will be affected.
Web site will show lotsa '?' ... for about 15-20 minutes.

This will be a longer than normal restart to get a lot more logging of the sequence numbers that I'm trying to resolve the issue in the new code.
It will actually be 2 restarts - so about twice as long.

It will be the shift summary after 01:00 UTC which should be a bit after 01:20 UTC

Thanks Kano!  It's great to always get heads-up information about the pool!

[not.you]

Hey Kano, how many addresses do you have that start with 1Kano?  Just curious.  I seemed to recall that it was your instructions that had allowed me to OC my jalapeno (thanks BTW) and I dug this up: https://web.archive.org/web/20140208185601/http://www.kano-kun.net/?p=70 and I noticed it has a different 1Kano... address then the one you use in association with the pool.  Sadly I also see that you never got a single donation to the address on that page.  My jalapeno did make a tiny profit but the little single was big loss or I woulda sent you something back then.

[kano]

CKDB restart complete ... and a block

[clgrissom3]

CKDB restart complete ... and a block

A Restart Block...way to go Kano!  Sweet!  This block was by mas41, a 41THs miner!  He gets on the Acclaim Board with his first kano block!

[HerbPean]

Antpoo scored like 20 sec after us with a huge 4.03KB block and 14 Transactions ....

[dragnaroc]

Hi Kano Miners,

Do I need to specifically do any config in order to get a block other then basic setup and mining in Kano pool?
Is it all depends on luck?
I am currently mining with 12 unit of S7.

[vh]

Hi Kano Miners,

Do I need to specifically do any config in order to get a block other then basic setup and mining in Kano pool?
Is it all depends on luck?
I am currently mining with 12 unit of S7.

that's about it.   create a login, set them up, point to kano.is with loginname.s701 - loginname.s712 (or equivalent) following the kano.is site instruction, and you're on your way to start getting steady bitcoins.   luck is welcomed but mostly optional.  

[dragnaroc]

thanks VH.
I am on the right path then.
started since 2nd of April.

So far so good. just hope to get a lucky block.

[vh]

thanks VH.
I am on the right path then.
started since 2nd of April.

So far so good. just hope to get a lucky block.

you have about a 1 in 155 chance to hit a block on a daily basis with that setup.   
if you hit a block before august, you are on the luck side of statistics.

double check for hw error, cooling, power supply, etc to improve hash rate in general to improve odds.
i can't think of anything else useful you can do to improve luck.   maybe rabbits foot, lucky sock, eat more chicken, if you want to test...

[dragnaroc]

thanks VH.
I am on the right path then.
started since 2nd of April.

So far so good. just hope to get a lucky block.

you have about a 1 in 155 chance to hit a block on a daily basis with that setup.   
if you hit a block before august, you are on the luck side of statistics.

double check for hw error, cooling, power supply, etc to improve hash rate in general to improve odds.
i can't think of anything else useful you can do to improve luck.   maybe rabbits foot, lucky sock, eat more chicken, if you want to test...

My S7 HW errors are below 0.001%, and temperature is always below 65 C.
well, then, i wish all of us a great luck on getting a block for ourselves.

[kano]

Anyone connected to the DE node, have all sorts of (linode) trouble with it for that last half hour.
Seems the linode DE network itself is ... screwed  at the moment.
Will post again once all is OK.

Connecting to DE from some places on the planet works OK now.
However, not everywhere, e.g. I can't connect to it directly, only via other servers.
Half the hash rate is back.
I suspect for most it is OK now, let me know if anyone can't connect (like me )