Solarpunk

5496 readers

101 users here now

The space to discuss Solarpunk itself and Solarpunk related stuff that doesn't fit elsewhere.

What is Solarpunk?

Join our chat: Movim or XMPP client.

founded 2 years ago

MODERATORS

ex_06

poVoq

SteveKLord

Solarpunk and web3 (self.solarpunk)

submitted 8 months ago by thisfro to c/solarpunk

40 comments fedilink hide all child comments

Note: I might just be uneducated on the subject.

When I read about web3 with blockchains, smart contracts and dapps, all sounds very promising. But once you look for any real world applications it is just some obscure things that kind of only exist to support the decentralized system. I guess that makes sense, but are there any actual real world uses for that? Like day-to-day things that make a persons life easier, not harder?

you are viewing a single comment's thread
view the rest of the comments

[–] danielquinn@lemmy.ca 6 points 8 months ago

Um, no.

Blockchains aren't databases because they can't store any useful amount of data. It's just a publicly-verifiable, append-only list of very small data points. To do something as simple as "look up who owned vehicle X on Y date" you still need a relational database engine like PostgreSQL, MariaDB, MSSQL, etc. Unless of course your application involves people downloading the entire chain locally and running your software on their machine to look up vehicle history. That'd work I suppose, but good luck deploying it, and it's a lot more work than an actual database.
Even if all you needed was a blockchain (you don't) the suggestion that they're easier to setup and publish on the web for public access than an actual database is laughable. You can get Wordpress up & running in about 10 minutes complete with a database, webserver and human-friendly UI to access basic tools. The idea that you can setup anything blockchain-based to be accessible to non-technical people in less than 10 minutes is just nuts.

A blockchain provides zero value to solving this problem. It's more complicated, doesn't lend itself well to web-based deployments, can't store the data we need, and requires the consumption of more energy than necessary while slowing down the process of adding records and making them more expensive.