Do i really need to go back thru my post history to find how many months ago i started barking about this.. ITS BEEN Far too long ago now.. Esp the size of the miner in question. Should have been more obvious to someone that is a great pool op or so caring of the miners like you say! guess ill check my first fb post and on here about this exact problem. Only to come to find out after 4 months i was right.. Seriously man defending slush makes you look the fool..
I'm not seeing four months of significantly bad luck here, just around mid December to maybe end January.
Heh you missed my post to you about the whole of December?
https://bitcointalk.org/index.php?topic=77000.msg13482822#msg13482822That's not four months though?
No idea about the previous months, just saying that was for the whole of December. And ridiculous bad luck.
Yep, you're right -- it was all December (1.26 for 228 blocks p>= 0.9998722) , not January (1.059126 for 202 blocks p>=0.8016885).
but it was going down hill two months prior to my dec 5 th post i just thought that it would correct.. i held my breath for two freaking months then i decided i needed to start bringing attention to this.. Thats why you dont see it for the whole picture.. There were so many days in those two months prior that we had 30 % block days of normal.. and then followed by several days of 70 %.. just because your weekly stats dont show the day to day.. it was much worse that it appears. Hell without the attacker who knows we could have been at kano standing of 106 % for the year instead slush was pushing to go lower than 90 % for the year.. and weekly stats he was barely finding more than 70 %.. im not going thru your weekly block maker stats organ but your know what im talking about. This started well before dec 5th its just wasnt till then when im like this cant be all variance!
Anyway. it is what it is.. you all seem to trust slush.. Lets see if he comes out with the brand and firmware of miners.. If that info never comes he was lying about the real reason for the shit luck.
https://slushpool.com/news/2016/02/06/recent-low-luck-information/https://bitcointalk.org/index.php?topic=1976.msg13183847#msg13183847 if you read from this message on other members chime in on them leaving months ago due to this!!.. just saying..
best Regards
d57heinz
EDIT What i think is happening here. is im compounding the issues he had prior to this.. which i think are all really related to
again i keep going back to server issues..
https://slushpool.com/news/2015/10/23/recent-orphaned-blocks-explanation/ He comments on facebook about this to a person and they say this..
Nepa Luzinka "Is soemthing cooking captain? three blocks on the trot without any fees ...."
Like · Reply · November 18, 2015 at 8:55pm
Slush pool
Slush pool "Hi Nepa, we have upgraded Bitcoind to new version yesterday and experiencing few difficulties. But we fixed it already and everything should be working fine now. wink emoticon"
Like · Reply · 1 · November 19, 2015 at 8:05am
But you have to remember for them to even start to think the orphans were a problem they let that happen for a month or so aswell.. i mean hell you cant let shit ride when its this serious!
And back in october going further back. he did some work on it to support bip 101 and then got attacked left and right.. EVER since that point on.. it has been going down hill. Starting with the orphans then all of sudden bad luck as well.> Orphans got fixed and then the bad luck continued to get worse.. then he decides that orphans arent the whole story.. >> A little honestly goes a long way.. I see a pattern of repeated failures going back as far as oct 2015 with the support of bip 101 (BTCXT)..