3 ms·
Thanks for the explanation and link. Reading it was like a train wreck...it's awful but you just can't look away. I don't see how that can be considered in any
by SwellJoe 15y ago
Thanks for the explanation and link. Reading it was like a train wreck...it's awful but you just can't look away.
I don't see how that can be considered in any way a reasonable limitation of the system. I had no idea the "coins" were so fragile.
Every time I think, "Hey, maybe it's time to start accepting bitcoin for our software. It can't hurt, and might even help spur adoption of new digital currencies." Something crazy comes along that makes me think bitcoin isn't so well thought out, after all. I was already a little worried about the "money" being stored on our world-facing system. I'd already assumed I would need to transfer to a private account every day or something to insure that a break-in of our web server (which has never happened in our 6 years of running it, but I know enough about system security to know that a determined attacker could eventually find a way in; which is why we don't store credit card data, software signing keys, or anything else particular sensitive on that server). But, this makes me think bitcoin, as implemented, all but guarantees coin loss, given enough time using the system...possibly very large losses, as in this case.
Seems that a system crash during a transaction would also lead to the same results. And even one bit of data corruption during saving data would do the same.
But, I guess this is the pain one experiences being on the bleeding edge. It wouldn't be called that, if somebody didn't bleed now and then.