Topic: HashFast announces specs for new ASIC: 400GH/s - page 181. (Read 880461 times)

Would anyone know the last order number shipped?

Hopefully. There's not much of substance to discuss at the moment. Those who want to take legal action are taking it. Those who want to wait on HashFast are waiting.

The death end of the thread

Something weird happened to me over the weekend.

I ordered this new 180gh/s BitCoin miner from a manufacturer yesterday. There wasn't a promise of 3 months in the future. They said they can ship it the next day (today).

So I did the usual ASIC supplier math, carried the ones, dotted the T's etc. and figured that means I'll receive it around the middle of March, end of February if I'm lucky. The ROI at BTC 1.45 still looked ok for then.

But then something weird happened... They actually shipped it today! And it's with UPS right now and I'm getting it tomorrow.

There was no excuses. No failed promises. No outright fraud. Whatever am I going to do with all the time I'm getting back by not fretting about miners? And no more re-scheduling of vacations so that I can be home for a specific promised delivery date that never materializes?

Just takes the fun out of life...


Ahh. There is, and always will be, the M.P.P. to look forward to.

I guess that we will start discussing batch 3 soon.

And what is the only possible conclusion to this?

They have the wafers, in stock, they have the PCB design, they have the building capabilities, yet, people don't receive those units. So, where do thoes units go?
I see subpoenas every-freaking-where.

But the waiting times for justice to make its course are boring.

Better buy bitcoins now then wait for that useless miner that is nothing worth and also cost much energy

Neither

Which comes first 100$ btc or MPP shipment?

I'm thinking that if Rascul thinks he chose manufacturers wisely, maybe he'll respond to that guy in the West African refugee camp.

   

    did i missed something in this thread?  ....  lol

DEAR HASHFAST,

1. Do something about your support email (Communication btween hashfast and your paying customers)
2. Refund incoming request by promisming and withdraw the refund directly after you receive your request)

Dear HF, please remember to buy cheap coins while they last.

Thanks.

(Or you could just build those machines that you promised us, at the speed that you promised us. Its up to you, really.)

Apparently Gmaxwell is a bitcoin core programmer?

Hmm, now he can officially say that HashFast has screwed the heart and soul of Bitcoin. (as one of their customers!)

Well good luck then with your Hasfaster miner, ur money is worther then that worthless machine now.

good stuff. and something perhaps we could all bear in mind; DELAYS. Personally i'm glad I bought HF, and not Black Arrow, or KnC, or Cointerra, for that matter.

I think we may have gotten the best of a bad lot. And I feel that, actually, i chose my manufacturer wisely.
to those screaming for a refund, please, be my guest, all you are doing is pushing others up the queue

 

Thanks for having decided to register to share your experiences, your technicalities, and you positive feedback about HashFast!



I'm personally starting to hope the price to crash so low that we will finally have a BTC refund!

Thanks MtGox!

Do anyone knows from the moment Hashfast request your refund how long it will cost before they send your money?? Anyone experience with this?

Did you have to do anything special to get your BabyJet running on Ubuntu (ie, is the included RPi doing much that's non-obvious?)? I've had no luck overclocking with the stock RPi (looks like a USB issue with the RPi at higher clock for some reason)....planning on putting the BJ on an Ubuntu laptop. Thanks!

Edit: this conv should probably be moved to the BJ Users' thread...

Not directly caused by a storm. I live in a town that has brown outs for any reason, including the wind blowing. This particular week it's been cold, and snowy. The power to this unit went out later in the day while I was at work, and my wife wound up turning it back on. Turns out in my run to plug the thing in, I didn't actually get it tied into a battery port but a surge port on my UPS. So yes, that period of drop was me losing power. Though not to a 'storm' like what you are thinking. More in general, to the cow farts that can cause our power around this town to blink and fritz.

But yes, I am a customer of HF. This is my babyjet that arrived on the 3rd of February, a day before we got some wonderful? snow and cold. It has been running on Ghash.io initially, and then subsequently I moved it to Eligius to compare to the results of those using the systems 'as delivered.'

I will note that from day one I overclocked it, and have not ran it on the Pi yet though I have two RPi's. It is actually tied into a VM I have running on one of my ESXi servers. Guest is Ubuntu 13.10 running currently the HF build of 3.9.0. I had tried the latest at the time 3.12.0 and had some instability, and when I moved to their version it ironed it out. Currently its running at 670 clock, and I've jacked it up to 720 and watched it do nothing but shut itself off. (which is the second dip immediately after the long drop, figured I'd push it further since it had been off a while.) You might see it drop some more due to me tinkering a bit and changing things up. I have not only CGminer on here, but mineproxy for my old blade that is now pointed at a solo pool playing the lottery. (just for grins) The system is also setup on my FogLight NMS with a reboot script applied if it sees any of my items not run. (CGMiner, MineProxy, etc.)

I posted my Eligius address, and also appended my sig JH's BabyJet to the message. (Which I'll go ahead and change to JH's OC'ed BabyJet, since that's more depictive.) ([Suspicious link removed]/1kaq3jA)

My experience both with HF and the BJ have been great. I've loved pushing the system since i got it, and am still tinkering with it. Everyone has had their own experiences, and their own opinions of the device.

Anyway, I return you now to your regularly scheduled thread.