Web3 has a storage layer, a messaging layer, and an execution layer. Most popular Web3 apps use Ethereum for execution, IPFS for storage, and some custom websocket garbage for messaging, but there are many viable Web3 stacks out there that people are using.
What actually defines web3 software? Is sending emails with .exe attachments considered web3?
Like, if we compare this to RESTful servers, there's no set definition but nearly everyone agrees it's verbs and paths over a hierarchical API sending JSON back and forth over HTTP[S].
It seems like most people can't agree on anything except using etherium as a backbone.
So calling something web3 doesn't seem to do a good job describing things like REST or like something like you wrote above.
