A blockchain can be decentralized at the protocol level while still depending heavily on centralized infrastructure underneath.
This is becoming one of the more interesting contradictions in Web3.
Users may interact with decentralized applications, but those applications often depend on a relatively small number of:
- cloud providers;
- RPC services;
- indexing platforms;
- node hosting companies;
- API providers;
- data availability services.
If a large percentage of an ecosystem relies on the same infrastructure providers, an outage at one company can affect dozens or hundreds of applications simultaneously.
This also creates regulatory and censorship concerns.
Imagine a network with thousands of independent validators, but most wallets and dApps query blockchain data through only a few large RPC providers. Consensus may remain decentralized, while access to the chain becomes much more concentrated.
This does not necessarily mean centralized infrastructure is bad. Economies of scale make these services faster and cheaper.
But decentralization probably needs to be evaluated across multiple layers:
consensus → hosting → RPC → indexing → front-end access.
Which layer do you think is currently the biggest centralization risk?
And are decentralized RPC networks actually becoming competitive enough to solve this problem?
Yes, that is a real concern because many projects depend on the same RPC, cloud and indexing providers. The underlying chain can be decentralized while the application layer still has several centralized points of failure.
@kate-ryzh Exactly — application-layer concentration is probably the part most users never notice until something breaks. I’d like to see more projects build in provider redundancy by default instead of treating RPC and indexing as single points of dependency.
This is a useful way to look at decentralization because consensus is only one layer of the stack. If wallets, RPCs and indexing all depend on the same few providers, users can still end up with a very centralized experience even on a decentralized network.