Yet another goddamned example of someone complaining about the Bitcoin network, when THEY are at fault, not Bitcoin.
In this particular event, the company sent out a Bitcoin transaction with no fee attached, which is not a good way to ensure the information is picked up by Bitcoin Nodes and put into the mempool queue.
See the problem? Oh right, NO FEE USED.
So there wasn't a DOUBLE SPEND, because if your transaction doesn't CONFIRM, then you haven't SPENT YOUR FUCKING BITCOINS properly. Any subsequent transaction depends on the inputs from the prior transaction being confirmed, and when this isn't the case, THAT transaction will be delayed too until the earliest one is done. (And until it does, or if it just goes into limbo - the coins are still in your balance.)
But again, we have people taking Bitcoin terminology and applying it in such a way as to cast doubt on the ENTIRE network.
Seriously, screw whoever is perpetuating this obvious shilling.
