This is a very good example of a government service that will be disrupted by blockchain. The US, Canada, UK versions are relatively good today. However, maybe El Salvador[0] needs a better way to manage its titles and hiring a software consultanting firm to build that would be “too expensive” (not including the variability in the final product - i.e. it could cost a lot and still suck) for it to be worthwhile.
Even for the service in the US there are still middlemen needed and it’s relatively clear that security is not a strong suit of corporate America let alone the revolving door of government contractors. In the long run it’s just cheaper to use the open source blockchain code built with first class security in mind. The standardized and public interface of a blockchain also lets other companies extend the services without the extra red tape, e.g. it would be nice to get notifications of my neighborhood housing getting sold, etc. But this is really a bonus and up in the air, the killer app is really for developing countries.
[0] not to pick on El Salvador I don’t know the quality of their services. I’m only using them because of the BitCoin stuff.
Same thing here. There is nothing to stop the government employee from putting incorrect data in the database.
This is why people see Crypto/Web3 as a solution looking for a problem. The complaint people have about the DMV isn't that their database gets hacked. The complaint is that the government workers do not care about doing a good or quick job.
I don't understand. Can you give an example?
A government is already a central entity. If you have some service controlled by a central entity, why not build it in the standard database-on-a-server approach which is much easier?