Topic: Round 15/16 KnC Jupiter, DZ MC. Please move comments and ?s to this thread. Thx. - page 7. (Read 14766 times)

I would LOVE for some things to be cleared up.  How about full disclosure and honest transparency as a start?




January 15th less 2 weeks =January 1st, 2 days after the move.

When you were asked what was in the back corner, you yourself commented "KnC, Redhash, and some Ants"

So if 3/4 of the facility is done and complete at the time of this picture, why wouldn't or couldn't you show us that?  Maybe because you didn't share virtually anything with us?  The silence was deafening.



On Jan 2 (+72 hours) Mapuao posted
On Jan 3 (+96 hours) madpoet posted
On Jan 3 (+96 hours - 4 days) you tell us:


On January 4th (+120 hours = 5 days) All miners were at 0

 
Then 2 miners started working sporadically for quite a few days.

Oj January 6 (7 days) Thomas posts that you are still yet moving equipment to a new breaker and scolds us for asking for updates.  We have been down 7 days at this point, a solid !@#$%^& week and he tells us "On another note we do have other things we need to get done than post a second by second breakdown of what's going on"

Did we EVER ask for second by second updates? We are 7 days into an outage with virtually NO information and we are basically told to quit asking!

On January 6 Thomas posts
I thought that the "new power" was already in and "upgraded"?  Yet you still maintain: "For the move itself we were down no more than 72 hours. Anything beyond that was equipment problems,"   At day 7 you were still messing with power, that is not an equipment problem.


The bottom line here is as I originally posted, the moved was botched, plain and simple.  This thread is proof of that.  We were told it was competent IT professionals hosting our investment "at a world class hosting facility". It is clear that was not the case.  You aren't fooling anyone on the thread, I have received quite a number of PM's in support of my stance and my vocal approach. I welcome any responses, public or private.

I exchanged quite a number of PM's with DZ during the outage and based on those decided to give you the benefit of the doubt, figuring you would do the right thing.  That clearly did not happen.  $150 off of hosting is a pittance.  Your botched move cost us 7BTC,  ~$5500!

It is disingenuous and incredibly insulting to all here that the blame is always placed elsewhere and no real responsibility is taken.  I am OK losing money to increasing difficulty, market conditions, low BTC value, true Acts of God etc.  Those are all real issues that are truly outside anyones control.  This botched move does not fall into those categories.

We placed our $$$ and our trust in you and we got screwed, royally.

To follow up I did receive the payout January 1. Sorry for the confusion.

Lets clear some things up.

Power was on at the facility from Hour #1. Comcast was not installed untill 5 days later. We still had internet and were mining during that time- just not on comcast.
What we didnt have untill last week was the UPGRADED power, IE the additional pulls.

For the move itself we were down no more than 72 hours. Anything beyond that was equipment problems, as in most of the jupiters and a few of the ants did not like the move for whatever reason.

Not to mention that picture- was taken before the move, before the coop's equipment was packed up. You cant even see the 3/4 of the place that is finished.

+1

We did lose a huge amount of time.  The 70% difference between payments shows that.  Difficulty could have only increased twice in a 2 week period, odds are it was only once.  I don't think it was by 70%.

M

72 hours?  Please go back and reread the thread. The miners went down on Dec 30 and the power and comcast weren't even installed until Jan 3!   Yes maybe you turned a couple miners on using generator power and a wireless connection, but nothing hashed for more than a few hours at best. 

Issues with the hardware?  That is because you moved it!  It was hashing perfectly prior to the move, a solid 20btc in the previous 2 weeks.  Yes difficulty went up, but we should have still seen at least 14 BTC for the period.

The real reason is that the move was botched, plain and simple.  It was poorly planned, poorly executed with no contingency or backup plan, plain and simple.  You provided little to no communication and what communication you did provide was merely blaming someone else for your lack of planning and telling us to quit asking!  You blamed everyone else and took NO responsibility.  That doesn't fly in my book.

Who moves hundreds of thousands of dollars of equipment to a new facility that doesn't yet have power or an internet connection?  Who orders parts to arrive on the very day that they are needed, such that when FedEx has a delay, THEY become the problem rather than taking responsibility for not ordering them sooner!  This is all coming from "access to 5 world class IT experts who have built the largest public Bitcoin Miners Cooperative in the English Speaking world" and a "world class hosting facility".  It is frankly insulting. 

Take a look at the pics of your "world class hosting facility" facility just "2 weeks" ago. It doesn't even look remotely ready for a move.  Check out the extension cords running to the miners near the door, are those our KNC's??? The reality is that the hardware was most likely damaged by running on dirty generator power and it probably damaged most of it, no wonder you are having issues with the majority of it.  But yet you blame KNC. Do they know the conditions it was ran in?

I have 20% of this group buy and the bottom line is your haphazard approach to this move has cost me dearly, to the tune of approx $1500.  This 40 mile move should have had less than 24 hours of downtime, and could have been done in 2-3 hours.  I myself have done several moves in my career with millions of dollars of equipment much more sensitive, and kept downtime to less than a day.  It can be done if you prepare and plan for it.  You didn't plan nor prepare and it cost us all, and cost us dearly.

It is a slap in the face to receive a $150 credit on hosting for your botched move. My 20% of that is $30.  That is what I would have made with about 4 hours of hashing at the old facility.  Lets see, down for 7 days and I get $30 and you call that fair?

Please take responsibility for what really happened. It is the very least you can do.

https://bitcointalksearch.org/topic/--7216

After looking back over the topic it seems 48 was wrong


The correct amount of downtime was closer to 72

Machines not working is not a hosting issue this is in reference to workers 2, 3 and 4 going down sporadically after January 2nd-3rd until a few days ago

48 hours? Are we in some sort of reality distortion field? It was way more than 48 hours, otherwise my payout would not be cut by 70% between two payments. I understand this is a risky business and people may get sick of whatever job they are doing, but saying these completely off the wall numbers is a bit disheartening. I do not ask for any compensation, but please don't let anyone say stupid shit like that. We were all here and this thread is a witness. I wish DZ MC a speedy recovery and successful future GBs since I am vested in them. Thanks.

Pretty much this. I may look into some other compensation a little later on, but this is all for now. I do apologize, but we have been working 14+ hr days for weeks now.

I believe that it is the Tx ID, but Thomas would have to confirm.

Here's some additional info from a PM from someone asking if there would be additional compensation for under performance on R15/16 and the move cross country:

"bobsag3 says they were only down for 48 hours even while doing the move through Winter storm Hercules. He says that is all the compensation for the move because he's giving a 25% discount on miner hosting when the miners were down 48 hours or 6% of the month for the move, and the rest of the problems have been hardware related with the miners from KnC. He doesn't feel that he's responsible for guaranteeing hashrate from faulty or badly performing hardware, esp. when they're from what are nearly universally considered one of the top ASIC manufacturers.

I don't know if you caught the updates but we've had issues with every single KnC miner (6 B1 and 6 B2 Jupiters) hosted by the co-op and Miner Hosting LLC's hosting customers:

https://bitcointalksearch.org/topic/m.4401660

I had updated my own opinions/reviews on the various ASIC mfgs with this new info: https://bitcointalksearch.org/topic/m.4437950

Not sure what else to tell you but that we *all* lost the same hashrate alongside with you because co-op leaders have our own shares in various amounts in this too, which is typical of these GBs. bobsag3 is so sick of these Jupiters that he's willing to let other miner hosts host these miners, if they want to take over the hosting.

...

Regards,
DZ"

Is this the transaction for the dividend 40432e38a774cc12132fab765228da9d2a3014f25c091e6a45b1c4b35c36c445 ?

Was there supposed to be a payout at the end of december? I got one in mid december and now another one in mid jan but nothing at the end of december.

I have a suggestion: don't touch them! They seem to be working fine now. We are almost at 50% ROI. Are you planning to move to another facility  ? I understand that's a crazy question, but I wasn't aware about previous move, so I don't know what questions I should ask.

Oh, I updated my ratings a few days later once I learned how bad the problems were:

https://bitcointalksearch.org/topic/m.4437950

I had to move them down to #3 with this new info. I reserve the right to admit I'm wrong or to update things as needed.

Bitmain. FTW! 

#2 is Up!

 

The average reply time for KnC is 48-36 hours... plus all the needles bulshit they make me do again to test it... means it can take weeks before I even get an RMA number. This is not my first time around the block with having to RMA modules.

EDIT: After god knows how many reboots and me cursing at it, it seems to have come back to life.

One week with 70% capacity. I would like to know answers. Thanks.

 

Yep, any news? There should have at least been an email by now?

#2 failed on January 6th. I wonder if we are in a LONG queue to get answers from KnC? Was it sent back?