3 ms·

Or, the provider, namely the government, can write the code to orchestrate these API calls even if these APIs are managed by disparate entities. It's not prete

Or, the provider, namely the government, can write the code to orchestrate these API calls even if these APIs are managed by disparate entities. It's not pretend like it's not a solved problem. It's just that you're trying to eliminate the central provider in this case and you want to replace that with a blockchain which is excruciatingly slow

freemanon 5y ago
A colleague of mine once disagreed to use git because it was easier for him to copy paste the project's folder every now and then to keep "versions" of his work. There are trade offs, but having data and core business logic in an open and transparent network would allow for better interoperability imo. Not saying there aren't fundamental issues to be solved with using blockchains, but it's a new path to be explored. The speed of the blockchain doesn't necessarily have to be slow. It depends on how decentralised and safe it needs to be. It's possible to create a "private" blockchain for some use cases. I don't see web3 as open in the sense of open to the whole world, but open to whoever the stakeholders are.