| > What do you propose other than a block chain for the public ledger? A csv file, SQLite file, mysql database dump, ... The blockchain is a distributed, trustless ledger, which is not necessary for most applications. If I may paint a picture of why this matters with an example from the gaming industry - simply because I'm familiar with it: There are projects being made where the inventory/achievement/whatever system lives on a public blockchain, so that you may use/display it in another game, website, whatever. But this already exists without blockchain! If you play Spiral Knights or Half Life on Steam, you get a hat in Team Fortress 2. There are various third-party websites where you can display your Steam/Team Fortress/Dota/LoL achievements, inventories, ... because those 'ledgers' are public already. You can trade Steam items on third-party websites (which interfaces with steam underneath) that dodge Steam's 30% store tax and will actually pay money out unlike Steam. The above applications only require public (or even just shared) ledgers. Distributed and trustless is not a requirement for these use cases. > And if your system uses cryptography for the transaction security and has a public ledger, why would you not call it a cryptocurrency? You could just as easily transfer USD, GBP or EUR using such a system. The currency itself need not be 'crypto' for the system itself to use cryptography for transactions. You wouldn't publish such a ledger for obvious reasons, but technically you can. |
A centralized MySQL database is not a "public ledger" in the same way that a decentralized blockchain is considered a "public ledger."
In the former, the database can be removed or censored easily by the central entity controlling it. This includes issuing API keys: the central controller decides who has permission to access, use, modify, and even retrieve the data.
In the case of a "decentralized, permissionless, public ledger" blockchain, no single entity controls the data structure.