I'm seriously considering requesting a refund and if they say no, I'm going to start the legal process.
Let's do this. We are already 3 people, 300$/hour divided by three, 100$ at hour for our lawyer. Seems almost reasonable. This is the email i got back: Hi *,
Thank you for your quick reply. Sorry to hear of the situation. You sent me an invoice, not a signed contract. Do you have a signed contract with the San Jose Company? A signed contract will show a written agreement and may have different terms.
According to the invoice you sent me, between pages 1 and 2 of the invoice it states your remedy and process for cancelling a future delivery because of delay and the refund process. It states:
"Baby Jet Delivery Dates. All of the 550 Baby Jet units from HashFast's first production batch are guaranteed for delivery by December 31, 2013. If Buyer ordered one or more units of such Baby Jets, and HashFast does not deliver such units by that date, then Buyer may cancel the undelivered portion of the order at Buyer's request and HashFast will refund the payment for the units that Buyer purchased but did not receive and cancelled. This cancellation and refund is Buyer's sole and exclusive remedy for HashFast failing to deliver by the December 31, 2013 guaranteed delivery date, and Buyer must cancel the order by January 15, 2014 to avail itself of this remedy. Buyer to pay all taxes, duties and shipping costs."
Have you communicated a need to stop the delivery and seek a refund from the sender company? Obtaining a cancellation before the December 31, 2013 date depends on whether you have a written contract with different terms and whether the sender company knew or promised that the delivery of the item(s) by a specific date. Do these apply to your situation?
If you wish to hire me, I charge $300.00 USD per hour and will require a $5,000.00 USD retainer up front and signed retainer agreement. At this time, I have not be retained by your or your company. I would say we should meet in person, but you are in *.
Thank you.
|
|
|
With a first of December delivery, standing to mining.thegenesisblock.com, we will lose 75% of our "investment". I can't even tell how i regret my bought.
If it makes you guys feel better, if Hashfast is delayed that means the network hashrate won't increase as much until they do start shipping. With knc shipping in volumes, i'm not sure that this is correct. Anyway i'm quite sure that the guy who bought 200+ will come out just fine. And apart from that, i would like to have a proof that the delay is really not depending from them/no hashfast chip will hash before the middle of next month. It wouldn't surprise me if "delaying" the shipment by "2 weeks" was a "decision" taken after the btc price spike. God, i'm starting to know hardware sellers so well that i should start my own.
|
|
|
With a first of December delivery, standing to mining.thegenesisblock.com, we will lose 75% of our "investment". I can't even tell how i regret my bought.
|
|
|
I'm contacting a lawyer in CA to see what can be done. PM me if you are interested in sharing the fees. (it's a preorder, and i'm demanding for a refund)
|
|
|
WE WANT ANSWERS you have our bitcoins!
4+ millions of dollars of them.
|
|
|
2 to 3 difficulty adjustments later = 2x to 4x the difficulty. Do i have to say how useless and overpriced these units are at that time? Batch 1 customers, MPP or not, will lose half or more of their investment. Probably more.
Is HashFast gonna do something over this or what?
Yeah, who's picking up the tab? We are basically paying double. November Batch rates. Anyway, if it's delayed up to (say) 3 years from now, when the hashrate is stable, our return would be sure (thanks to MPP). The only case in where the mpp works, is that one.
|
|
|
2 to 3 difficulty adjustments later = 2x to 4x the difficulty. Do i have to say how useless and overpriced these units are at that time? Batch 1 customers, MPP or not, will lose half or more of their investment. Probably more.
Is HashFast gonna do something over this or what?
|
|
|
Yes puppet, good point. Had to view the page source to reach the image...
|
|
|
I have a lot of BJ in preorder from HashFast, they should be delivered by the end of the month. Updates on delivery should come today. I'm reselling them at cost. Offer includes Miner Protection Plan.
If you are interested into the offer with hosting already included (free for the first year, tier 3 datacenter), just send to this address whatever amount (make sure that you can receive from the sending address and that you have the private key (Eg, you can sign messages)): 1Mdco7wnn3em8WYdALNYGPzf4zksePLKKp
I can provide proof of purchase to a mod if required. Please also check my trust history, i won't use an escrow for the hosting solution, while it's welcome with the bare hardware purchases.
Contact me for every question.
|
|
|
Where is our update? I'm tired of this bs.
|
|
|
Yes, actually. We anticipate making an official announcement today. Let's see if it's a vapourware type announcement or what. And let's see if it's today or in 2 weeks.
|
|
|
Yes, actually. We anticipate making an official announcement today. Let's see if it's a vapourware type announcement or what.
|
|
|
Hashfast, any proof that you have something to deliver pretty soon would be appreciated for our mood. I'm getting more sad every time i visit the thread.
|
|
|
no chips...no case...no design...no refunds...
But the best pr ever.
|
|
|
Exhausts on the side doesn't make any sense in any way you look at it. Datacenter racks are death easy: cold air on the front, warm on the back; there is no side intake or bs like that, there are other servers on the side. Just flip the psu 180 degrees and you have a working design.
Admittedly a rather maverick design idea of hashfast, but probably no big problem. The PSUs only have to exhaust their own heat, which should be negligible. I don't care about the PSUs. I care about the fact that they don't know how a PSU and a rack works. Who have i paid? Elementary school boys?
|
|
|
Btw, i'm still waiting for the pics of the finished BJ cases promised a week ago,
and,
For the now promised shipping date, that no one wants to give me. Firsts days of november? We got a problem.
|
|
|
Exhausts on the side doesn't make any sense in any way you look at it. Datacenter racks are death easy: cold air on the front, warm on the back; there is no side intake or bs like that, there are other servers on the side. Just flip the psu 180 degrees and you have a working design.
I can't believe i bought from you guys.
|
|
|
Guys, i've yet to understand to what date we have to sum this week of delay to. 17 of october? 25 of october? 30 of october? And what's this expensive (for our pockets) component? Are you running out of capacitors? (avalon did, remember?)
Up. Up. Plus: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fhashfast.com%2Fwp-content%2Fuploads%2F2013%2F10%2F4U-front-perspective-TOP-OFF-1024x768.jpg&t=663&c=tVeYkBvJutzdWw) Please tell me that there is a good reason to put the PSU air intake there, in a spot that once in a rack, no air can come trough. And if such a good reason doesn't exist, i HAVE to conclude that it is only a rendering of a non existing case for something that will not ship anytime soon done and approved from people that doesn't have any idea of what they are doing.
|
|
|
Ammetto che quando ho scritto hashing di chiave privata ci ho pensato un secondo, ho realizzato che non aveva molto senso potendo usare quella pubblica, ma poi ho erroneamente supposto che nessuno avrebbe notato la differenza ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Il tuo ragionamento è sbagliato, perchè l'indirizzo btc ha (intrinseco) un checksum, in modo che una stringa casuale di 34 caratteri che inizi con 1 non possa essere scambiata per indirizzo btc. Io comunque quando calcolo questa difficoltà faccio un altro ragionamento sbagliato, ovvero utilizzo la chiave privata; l'indirizzo btc è un hash della chiave privata, quindi contiene meno entropia.
2^256-1 è circa il numero di atomi presenti nell'universo osservabile.
Buona fortuna a beccare due atomi uguali.
Per ora non è mai stato dimostrato un attacco di collisione tra due hash SHA2-256, cosa che non si può dire per ad esempio MD5.
Ciao.
|
|
|
|