Earlier quoted context omitted.
> only charge a tiny margin over the costs of bandwidth, energy and storage. The margin charged in terms of energy is massive . The bitcoin network can't handle many TPS because each transaction needs significant computational work to secure it. On the other hand, if I trust my database I can do the tiny work to write it, make sure I've got consensus among my DB nodes it's written, and be done with it. I'd say that b…
That's not even a little true. The transaction requires little/no work whatsoever. The miners require precisely as much work as there is speculative value for bitcoin. If Bitcoin were worth $10,000 per bitcoin - the energy burned per transaction would be 40 times higher. But that is not to say that the transaction itself required this expense. Mt Gox had as much to do with bitcoin as it did to do with http. I wouldn'…
As you say, the energy burned should be proportional to the value of bitcoin; if I have 100 BTC then I have a vested interest in mining outside of gaining new BTC -- I also want to protect the BTC&transactions I have from attacks.
The argument that it's okay to spend that amount of money securing that amount of money, however, is nonsensical.
Transactions in traditional databases do take almost no work. There's no thousands of computers computing and discarding hashes just to be able to add and subtract some numbers.
I'll acknowledge that MtGox isn't a good thing to reference here, but the fact of the matter is that bitcoin is rife with things that a regular man would call "unreliability".
I don't appreciate that you immediately condescend that I don't understand anything to do with bitcoin when your response has little substance.
Your response is basically "transactions don't require that energy is burned but energy is burned for transactions" and you have the gall to say I don't understand anything?