innerchaos
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 02:15:51 AM |
|
yea it just came back up for me too, and it false reported a block found on the android app...
|
|
|
|
innerchaos
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 02:17:25 AM |
|
and another false report on the android app.. ok now this block is just teasing us..
|
|
|
|
WBF1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 02:27:23 AM |
|
and another false report on the android app.. ok now this block is just teasing us..
probably has more to do with how the app is detecting new blocks than anything with the pool itself.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 02:31:13 AM |
|
Just a small update to the ckdb back end. Of course no effect on mining. The workers page now includes a "Share Rate" This is calculated from the shares you have submitted back to the last time your worker was idle A ckdb restart will also reset the "Share Rate" back to zero. This is for those who think that waiting 60s to see a random number hash rate is too slow ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) You now get to see a random number hash rate (under "Share Rate") as soon as you submit a share to the pool after you first connect. By "random number" I am of course referring to the fact that although no hash rate shown on any pool is accurate (since even the miner doesn't accurately know it's own hash rate) the shorter the time frame in which you calculate the hash rate, the more random the result is. Even at 1 minute it's far from accurate no matter how anyone calculates it.
|
|
|
|
thedreamer
Legendary
Offline
Activity: 1694
Merit: 1002
Go Big or Go Home.....
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 03:11:12 AM |
|
This block is just ridiculous. ![Cry](https://bitcointalk.org/Smileys/default/cry.gif)
|
Go Big or Go Home.
|
|
|
aarons6
Legendary
Offline
Activity: 1736
Merit: 1006
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 04:23:40 AM |
|
even antpool is having really bad luck, down to 65%..
wonder if its some kind of block attack someone figured out?
|
|
|
|
SergES
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 81
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 06:22:57 AM |
|
Record - 406%.
|
|
|
|
Digitalmocking
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 06:44:47 AM |
|
Record - 406%.
Nope, we've seen bigger.
|
|
|
|
Digitalmocking
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 08:49:03 AM |
|
Did we have a pool restart a few minutes ago?
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 09:44:57 AM |
|
Did we have a pool restart a few minutes ago?
Was a restart at 08:40 UTC One of the top miners went berserk dropping and disconnecting madly. The guy I usually ask about them is asleep so I reset all the connections with a restart (so should have been few if any failovers) Didn't really solve the problem but his miners have settled down a lot now an hour later so I can only presume it was a network problem at his end. Would seem I need to sacrifice something more to appease the block Gods ... Maybe the pool restart can do it ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
thedreamer
Legendary
Offline
Activity: 1694
Merit: 1002
Go Big or Go Home.....
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 11:10:53 AM |
|
Are you sure nothing is wrong? It started not solving right after the last update or whatever changes you've made. I have not seen it this long in 4 months if I remember correctly. ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) Not a blame, but with the hash I've been sending over the past few days, it's starting to hurt.... ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
Go Big or Go Home.
|
|
|
LoneRangir
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 11:34:31 AM |
|
This block is just ridiculous. ![Cry](https://bitcointalk.org/Smileys/default/cry.gif) Before I found this pool, I was part of a 99.6 CDF block over at bitminter. That amounteted to a ~5 day drought, too. I'm getting eager myself. I just bought an S4 off of CL, and I'd like to get rewarded for putting up with all this noise!
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 12:35:14 PM |
|
Are you sure nothing is wrong? It started not solving right after the last update or whatever changes you've made. I have not seen it this long in 4 months if I remember correctly. ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) Not a blame, but with the hash I've been sending over the past few days, it's starting to hurt.... ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) Unfortunately, it's expected, on average to happen every so often on every pool. 1.83% of blocks are expected on average to be over 400% That's an expected average, not an absolute value. As I've mentioned on the previous page, so far, the longest block was 593.99% Here's some info on all the ones above 400% https://bitcointalk.org/index.php?topic=789369.msg11440377#msg11440377So this is the 4th block on the pool to be above 400% since we started.
|
|
|
|
pekatete
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 02:30:13 PM |
|
Are you sure nothing is wrong? It started not solving right after the last update or whatever changes you've made. I have not seen it this long in 4 months if I remember correctly. ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) Not a blame, but with the hash I've been sending over the past few days, it's starting to hurt.... ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) Interesting whether the drought has struck the solo pool as it has here as well ..... that'd insinuate the fix that thwarted the block-attack / network test is playing with our luck! Saying that, it may just as well be the other pools coining on to the "fixes" ck put in his code ..... either way, this is rotten luck to say the least.
|
|
|
|
Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 04:40:22 PM |
|
It's easily explained by looking at the last 20 blocks solved by the pool, they're all nice and green except 2; that can't continue. This drought should be expected and should be expected to last long enough to bring the pool luck back to average; it has 0 to do with any changes to the code or whatnot.
|
|
|
|
pekatete
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 05:10:32 PM |
|
^^ Not sure your opinion counts for anything on this one ..... It is ck who posted (during that good luck streak that coincided to an extent with the network test) that he'd made some changes to the code with the insinuation those changes were responsible for smoothing, aka improving the pool's luck during that storm. Someone else raised the query as to whether those same changes (whose announcement roughly coincided with the start of the bad luck streak) could be playing a part in the current bad luck streak.
I am sure they have looked at the code numerous times since then, doesnt stop me from pondering the question (and wondering whether the same bad luck affliction has befallen the solo pool which I assume also carries those changes).
|
|
|
|
thedreamer
Legendary
Offline
Activity: 1694
Merit: 1002
Go Big or Go Home.....
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 06:26:14 PM |
|
It wasn't an opinion not accusation, so please gtfo.
|
Go Big or Go Home.
|
|
|
pekatete
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 06:45:25 PM |
|
This bad luck stretch is surely getting most tetchy ... squeeky bum if you like (well, over 5 days, who'd blame who?)..... on the positive side, the invalids' % is consistently getting lower, and that should qualify as an attributable result of rubber chicken sacrifice.
|
|
|
|
Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 06:47:15 PM |
|
^^ Not sure your opinion counts for anything on this one ..... It is ck who posted (during that good luck streak that coincided to an extent with the network test) that he'd made some changes to the code with the insinuation those changes were responsible for smoothing, aka improving the pool's luck during that storm. Someone else raised the query as to whether those same changes (whose announcement roughly coincided with the start of the bad luck streak) could be playing a part in the current bad luck streak.
I am sure they have looked at the code numerous times since then, doesnt stop me from pondering the question (and wondering whether the same bad luck affliction has befallen the solo pool which I assume also carries those changes).
Not sure my "opinion" counts? Well I'm not giving you an opinion, I'm stating facts. You made the "smoothing" statement, not ck. It's a couple pages back, I just found it. Those pool changes were made July 10 right before the pool went on a 14 block <100% rampage. How that coincides with the start of this "bad luck block" is beyond me, maybe you can explain? Or not, because really I don't care about your speculation. Luck is luck, nothing you can do changes it, stop pondering.
|
|
|
|
thedreamer
Legendary
Offline
Activity: 1694
Merit: 1002
Go Big or Go Home.....
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2015, 06:55:22 PM |
|
^^ Not sure your opinion counts for anything on this one ..... It is ck who posted (during that good luck streak that coincided to an extent with the network test) that he'd made some changes to the code with the insinuation those changes were responsible for smoothing, aka improving the pool's luck during that storm. Someone else raised the query as to whether those same changes (whose announcement roughly coincided with the start of the bad luck streak) could be playing a part in the current bad luck streak.
I am sure they have looked at the code numerous times since then, doesnt stop me from pondering the question (and wondering whether the same bad luck affliction has befallen the solo pool which I assume also carries those changes).
Not sure my "opinion" counts? Well I'm not giving you an opinion, I'm stating facts. You made the "smoothing" statement, not ck. It's a couple pages back, I just found it. Those pool changes were made July 10 right before the pool went on a 14 block <100% rampage. How that coincides with the start of this "bad luck block" is beyond me, maybe you can explain? Or not, because really I don't care about your speculation. Luck is luck, nothing you can do changes it, stop pondering. Don't bother with him. He's always been a troll.
|
Go Big or Go Home.
|
|
|
|