People interact with open-source applications like MetaMask, Web3 games, the metaverse and DeFi protocols every day but don’t often stop to think about what happens in the background for it all to work. If we think of Web3 as a burgeoning new city, node infrastructure providers are the underlying power grid that makes operations possible.
All DApps need to communicate with blockchains, and full nodes serve billions of requests from DApps to read and write data to chains every day. We need a huge node infrastructure to keep up with vastly expanding DApp ecosystems and serve all of the requests. However, running nodes is very time and capital intensive, so DApp builders turn to providers for remote access to nodes. There is a massive monetary incentive for infrastructure providers to power as many of these Web3 ecosystems as possible, but who is winning this race so far?
The fastest way to provide reliable infrastructure to power DApp ecosystems is for centralized companies to set up a fleet of blockchain nodes, commonly housed in Amazon Web Services (AWS) data centers, and allow developers to access it from anywhere for a subscription. That is exactly what a few players in the space did, but it came at the price of centralization. This is a major issue for the Web3 economy, as it leaves the ecosystem vulnerable to attacks and at the mercy of a few powerful players.
Consider that over 80% of Ethereum nodes are located in the United States and Germany, and that the three largest mining pools could come together to 51% attack the network. In many ways, today's blockchains are a lot more centralized than we'd like them to be, in stark contrast to the ethos originally set out in Satoshi Nakamoto's Bitcoin (BTC) white paper.
If
Read more on cointelegraph.com