This has been a pet-peeve of ours for a while now. Web3 has been skewed towards the blockchain / network providers, which translated into forcing debilitating constraints on developers and users. It stems from the fact that, ceteris paribus, chains tend to be incompatible with one another. Cross-chain transactions require a bridge or other cumbersome solutions. Those are, for most users, insurmountable. We’re not implying a conspiracy. We’re saying that differences in architecture and deployment technologies created a mono-chain, segregated reality, and that the burden it incurs is being carried by the developers and users. Perhaps an example will illustrate. Imagine a DApp (let’s say it’s an NFT game with a name that rhymes with Kabook). It decided to develop on X infrastructure for example AT&T. The potential market for the DApp is anyone who likes the game, regardless of the infrastructure they are familiar with. However, if a user is accustomed to using a different infrastructure, one that uses, for example, Verizon, functioning across the providers(e.g., moving funds) is not trivial. To convert that user, the DApp needs to invest effort not only in convincing him to adopt the game, but also in convincing him to adopt a new provider.