Coinbase did not intentionally send out transactions that were likely to never confirm, but they recognized that it was their responsibility to make sure that their customers got paid. So they offered a bounty for the confirmation of your mistake, and they fixed their program so they wouldn't use unconfirmed inputs in transactions again.
I have emailed several pools when this problem occurred, and offered a bounty. The bounty was small, but it was something.
I see that the coinad.com website is till up and running. Have you fixed your process to ensure that you don't send large transactions with small fees yet? Have you fixed your process to ensure that you don't double spend any inputs again?
I said in a previous post that payments are suspended. It will remain like that until I find a way to prevent this.
Whew, glad coinbase is making good, and improving their service.
I should like Carlos L. to reconsider his business model and research suggested fees for the large(in bytes) transactions he does. I would suggest that people use
http://bitcoiner.net, there you can go back multiple days and not take a payout until it is larger. This makes the fees on both sides more manageable.
I'm already working on it.
Show Posts
.5 btc to make the server or make an offer
