If BFL has enough funds to offer the bumping facility a "blank cheque", then they have enough funds to engage someone to troubleshoot this project. Josh is clearly out of his depth in terms of managing customer expectations - it's time to hand that job over to someone else because this isn't going to end when Batch 1 ships.
People want credible reassurances that the schedule for the second 6,000 chips is going to be better managed, and especially that the batch of 75,000 chips is going to be made into actual units and shipped some time this year. Someone needs to get this project back on track and they need to explain to existing and potential customers how that's going to happen.
Deflecting blame to the bumping facility is unacceptable. It's up to whoever's in charge of the project to ensure that contractors are chosen wisely, that contracts are locked down, and that contractors are provided with what they need to do their job (if your chip is so dense that creating the mask will take extra time at the fab or that the absence of an alignment wafer will slow down bumping, it's
your responsibility to know that).
Even if the bumping facility burns down with the chips, there should be enough insurance on the project to refund customers whose orders are affected.
BFL should cease taking any further pre-orders until this project is back on track and they can offer delivery in a reasonable time-frame.
Edit. What in the hell is going on that Josh feels it would be inappropriate to disclose publicly? People with pre-orders are undoubtedly stakeholders, but they're not necessarily entitled to the same level of detail as investors or board members. Seriously, if you can't provide enough information publicly to reassure your existing customers, then why on earth should they trust you for another day instead of cancelling their orders right now? And why should any potential customer take a chance on ordering with you?
https://forums.butterflylabs.com/bfl-forum-miscellaneous/1034-february-14th-2012-update-discussion-thread-12.html#post16015Reassurance needs to be as public as possible right now.