19
Solarpunk and web3
(slrpnk.net)
The space to discuss Solarpunk itself and Solarpunk related stuff that doesn't fit elsewhere.
Join our chat: Movim or XMPP client.
You can do this in about 20min with an actual database.
Blockchains aren't capable of storing any significant amount of data, so at best you'd still have a normal database and an overengineered verification layer. Even then, you still haven't solved the actual problem: availability of the data.
The reason it takes a long time to retrieve the information you want is that it's not already in a searchable database, so someone has to be paid to look it up by hand and create a report for you. If the people with the data were to simply publish a CSV, you'd get everything you need without having to waste time, money, and energy on a blockchain.
It actually ran on MSSQL, the issue was connecting every previous owner and service report to that vehicle. They did that by hand because it was cheaper.
A blockchain is just a very different database engine and it would be easy to deploy for this with very low cost. With a traditional DB you need a developer for both a front and backend so customers can get the data themselves while most blockchains are pisseasy to set up and configure to your needs and have a ton of open source frontends to choose from and you only end up needing someone to redesign the page.
Um, no.
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.