Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2196. (Read 5352067 times)
January 13, 2015, 07:09:57 PM
CEX and a couple other cloudfarms shutdown with the latest diff change. That's probably most of it for now.
January 13, 2015, 07:06:12 PM
It is because of the drop in BTC price, probably a lot of people are no longer seeing a profit so they are shutting down until price goes back up. It won't affect us much right now, the difficulty just changed yesterday (I think), maybe it will eventually, someone with more knowledge will need to answer that.
that's a 130pH Zach....that 's a lot of people
January 13, 2015, 06:37:52 PM
Added a rolling 1 hour average to: http://ckpoolmonitor.zachmonroe.com/
January 13, 2015, 06:01:24 PM
Wow, looks like there some farms shutting down.
Check out the last 30 days Hashrate on
https://blockchain.info/charts/hash-rate?timespan=30days&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=
dropped from 358,478,281 GH as low as 229,513.534 GH ..
sword taking another break?LOL
Seriously though, comments? Big farms shutting down? Impact difficulty? What about us little guys?
Check out the last 30 days Hashrate on
https://blockchain.info/charts/hash-rate?timespan=30days&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=
dropped from 358,478,281 GH as low as 229,513.534 GH ..
sword taking another break?LOL
Seriously though, comments? Big farms shutting down? Impact difficulty? What about us little guys?
Some farms are shutting down, but that's also bad luck.
January 13, 2015, 05:34:11 PM
Payout 338713 sent (a while ago) and confirmed
January 13, 2015, 05:30:12 PM
It is because of the drop in BTC price, probably a lot of people are no longer seeing a profit so they are shutting down until price goes back up. It won't affect us much right now, the difficulty just changed yesterday (I think), maybe it will eventually, someone with more knowledge will need to answer that.
January 13, 2015, 05:02:09 PM
Wow, looks like there some farms shutting down.
Check out the last 30 days Hashrate on
https://blockchain.info/charts/hash-rate?timespan=30days&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=
dropped from 358,478,281 GH as low as 229,513.534 GH ..
sword taking another break?LOL
Seriously though, comments? Big farms shutting down? Impact difficulty? What about us little guys?
Check out the last 30 days Hashrate on
https://blockchain.info/charts/hash-rate?timespan=30days&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=
dropped from 358,478,281 GH as low as 229,513.534 GH ..
sword taking another break?LOL
Seriously though, comments? Big farms shutting down? Impact difficulty? What about us little guys?
January 13, 2015, 04:21:54 PM
Heh I did actually have some code to solve this - so I fired up the command and it's now fixed.
71.65% - another sub 100%
https://bitbucket.org/ckolivas/ckpool/src/43dc33a54caefc130570d403d8f95e89efa88c04/src/ckdb_cmd.c?at=master#cl-1003
Ever better 71.65% - another sub 100%
https://bitbucket.org/ckolivas/ckpool/src/43dc33a54caefc130570d403d8f95e89efa88c04/src/ckdb_cmd.c?at=master#cl-1003
it was actually 36.83%In case anyone was curious, the confirm set the block to the current in code numbers, but then a later check, resets them to the correct numbers based on the blocks range.
So this will also affect the next block (unless I restart ckdb before that)
It will show up as about 35% below what it really is on the web page and the first confirm stage.
But it will correct it about 20 seconds later with the correct values.
So until we get the next block, that number at the top will be about 35% below what it really is.
Either way 3 quick blocks are nice.
I did some fast math. pool has about 4000th right now
pull out the top 4 as they are too high pool drops from 4000th to 568 th
pull out ck and kano pool drops to 558 th pull out the bottom under 800gh
and the remaining qualified to win people have about 550th running so if you are running 2 sp20's at 2.5 th you have 2.5/550 chance to win. or about 220 to one.
if you are running 1 sp20 at 1.4th you have around a 400 to 1 chance to win.
If one of us can get lucky by block 100. Or it goes to Volley I think.
Edit HST is the default winner?
January 13, 2015, 04:10:01 PM
Heh I did actually have some code to solve this - so I fired up the command and it's now fixed.
71.65% - another sub 100%
https://bitbucket.org/ckolivas/ckpool/src/43dc33a54caefc130570d403d8f95e89efa88c04/src/ckdb_cmd.c?at=master#cl-1003
Ever better 71.65% - another sub 100%
https://bitbucket.org/ckolivas/ckpool/src/43dc33a54caefc130570d403d8f95e89efa88c04/src/ckdb_cmd.c?at=master#cl-1003
it was actually 36.83%In case anyone was curious, the confirm set the block to the current in code numbers, but then a later check, resets them to the correct numbers based on the blocks range.
So this will also affect the next block (unless I restart ckdb before that)
It will show up as about 35% below what it really is on the web page and the first confirm stage.
But it will correct it about 20 seconds later with the correct values.
So until we get the next block, that number at the top will be about 35% below what it really is.
Either way 3 quick blocks are nice.
I did some fast math. pool has about 4000th right now
pull out the top 4 as they are too high pool drops from 4000th to 568 th
pull out ck and kano pool drops to 558 th pull out the bottom under 800gh
and the remaining qualified to win people have about 550th running so if you are running 2 sp20's at 2.5 th you have 2.5/550 chance to win. or about 220 to one.
if you are running 1 sp20 at 1.4th you have around a 400 to 1 chance to win.
January 13, 2015, 03:37:39 PM
Heh I did actually have some code to solve this - so I fired up the command and it's now fixed.
71.65% - another sub 100%
https://bitbucket.org/ckolivas/ckpool/src/43dc33a54caefc130570d403d8f95e89efa88c04/src/ckdb_cmd.c?at=master#cl-1003
Ever better 71.65% - another sub 100%
https://bitbucket.org/ckolivas/ckpool/src/43dc33a54caefc130570d403d8f95e89efa88c04/src/ckdb_cmd.c?at=master#cl-1003
it was actually 36.83%In case anyone was curious, the confirm set the block to the current in code numbers, but then a later check, resets them to the correct numbers based on the blocks range.
So this will also affect the next block (unless I restart ckdb before that)
It will show up as about 35% below what it really is on the web page and the first confirm stage.
But it will correct it about 20 seconds later with the correct values.
So until we get the next block, that number at the top will be about 35% below what it really is.
January 13, 2015, 03:22:19 PM
It may be an orphan one 
.
.it appears on blocktrail dot com as ours and not an orphan. shares are registering, so i think we'll be all right... and of course our pool is ran by 2 of the best tech guys in the community.
Right On!
Funny thing is that bitcoind said it was rejected, but the network accepted it.
Will fix it up so that it displays properly of course.
(P.S. yes I was asleep
) January 13, 2015, 03:14:53 PM
It may be an orphan one .
.it appears on blocktrail dot com as ours and not an orphan. shares are registering, so i think we'll be all right... and of course our pool is ran by 2 of the best tech guys in the community.
Right On!
Funny thing is that bitcoind said it was rejected, but the network accepted it.
In ckdb, blocks go through stages, first stage is "New" (as it shows on the web) then "1-Confirm" once ckpool says bitcoind accepted it.
That 2nd stage didn't happen, so ckdb didn't take the next step of checking the validity of the block.
Of course, this hasn't happened before and I don't handle it in the code, so ckdb thinks it's stuck at "New".
Will fix it up so that it displays properly of course.
(P.S. yes I was asleep
)Make sure you get plenty of rest bro. We hit a lot of blocks pretty quickly since the contest started.
January 13, 2015, 03:13:11 PM
It may be an orphan one .
.it appears on blocktrail dot com as ours and not an orphan. shares are registering, so i think we'll be all right... and of course our pool is ran by 2 of the best tech guys in the community.
Right On!
Funny thing is that bitcoind said it was rejected, but the network accepted it.
In ckdb, blocks go through stages, first stage is "New" (as it shows on the web) then "1-Confirm" once ckpool says bitcoind accepted it.
That 2nd stage didn't happen, so ckdb didn't take the next step of checking the validity of the block.
Of course, this hasn't happened before and I don't handle it in the code, so ckdb thinks it's stuck at "New".
Will fix it up so that it displays properly of course.
(P.S. yes I was asleep
) January 13, 2015, 03:11:31 PM
January 13, 2015, 02:56:17 PM
It may be an orphan one .
.it appears on blocktrail dot com as ours and not an orphan. shares are registering, so i think we'll be all right... and of course our pool is ran by 2 of the best tech guys in the community.
Right On!
January 13, 2015, 02:48:55 PM
It may be an orphan one .
.it appears on blocktrail dot com as ours and not an orphan. shares are registering, so i think we'll be all right... and of course our pool is ran by 2 of the best tech guys in the community.
January 13, 2015, 02:31:32 PM
It may be an orphan one .
. January 13, 2015, 01:19:43 PM
The status of block 338787 is stuck on the pool website. Shows it as NEW but over 6 confirms on blockchain.
Yeah, I was noticing the same thing. Strange.
January 13, 2015, 01:15:22 PM
So the winner wil be Lightsword or Bitminerpro....
The winner wil be SP20winner
bwahahaha, quality name whomever did that.
January 13, 2015, 01:11:34 PM
The status of block 338787 is stuck on the pool website. Shows it as NEW but over 6 confirms on blockchain.
Jump to: