Is the current Web3 really decentralized?
However, at this point where we can already interact with many Web3 applications, we must ask ourselves the question: Is the current Web3 really decentralized? The short answer is: No. And as shocking as it may be, that is the reality today, a reality that must be accepted, reviewed and overcome.
Let's put for example OpenSea. This acquaintance market of NFTs is considered one of the most important DApps (Decentralized Applications) in the ecosystem Ethereum, Polygon y Solarium. And we say “DApp”, although the truth is that OpenSea as it is, is far from decentralization. If you try to access OpenSea from a country banned by the United States, you will not be able to enter and enjoy its services, which, by the way, are neither military nor espionage nor anything malicious. A simple market NFTs vetoes access to its users because it depends on third-party infrastructures created in order to filter who can and who cannot access said website and therefore the DApp, all because of the wishes of a third party.
Faced with this reality, many in the community tend to respond that OpenSea's "DApp" is in Ethereum and their smart contracts are available to everyone. The latter is true, but they forget that interacting with a smart contract is not easy at all, and for a novice, it is the same as handling a passenger plane in a dive, with engines off and without flight controls. OpenSea is not just “the smart contracts on Ethereum”, it is its interface and all the amount of work that makes using OpenSea easy for everyone who uses the application.
A core problem to be overcome
It is clear at this point that the current Web3 is not fully decentralized and, although there is much progress in achieving it, we still have a long way to go to achieve true decentralization in Web3.