• 0 Posts
  • 143 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle










  • Zoolander@lemmy.worldtoMemes@lemmy.mlBlockchain: the wave of the future
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    9 months ago

    The only person here who doesn’t know what they’re talking about is you. If you took a standard DB (MySQL or Postgres, for example) and took that same information and stored it on a blockchain instead, you’d use far more energy on the blockchain and the issue would only get exponentially worse as the chain got bigger. Normal DBs don’t need to hash new entries or validate them against previous entries that are also hashed.





  • Zoolander@lemmy.worldtoMemes@lemmy.mlBlockchain: the wave of the future
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    9 months ago

    DBs are not the same as a blockchain. A DB doesn’t have to hash all previous data before it every time the DB is written to. You can read and write to a specific spot in a DB without ever knowing anything else about the DB. With blockchain, inserts have to be successive and they have to reference every previous insert to validate that the entry series is unbroken. On top of that, for things like Bitcoin, every other client also has to validate it since the ledger is shared.

    There’s a reason blockchain is significant. Otherwise, why didn’t stuff like Bitcoin exist prior to it? Databases, in some for or another, have existed for decades. Blockchains are immutable, that’s why. The order of entries matters and validation is a requirement.