We might as well divide the front-end decentralization process into three parts: browser, decentralized domain name, decentralized storage, and computing.

Most browsers can complete the access of decentralized domain names. It is worth noting that, since current web browsers do not support decentralized domain names, access to decentralized domain names requires centralized access port bridging. But the exciting thing is that many browsers are beginning to support decentralized storage IPFS and computing, including mainstream browsers such as Chromium, Firefox, Opera, Brave, etc. They all support encrypted wallet plug-ins, and some of the platform versions of Opera and Brave already support The native access capabilities of IPFS and ENS domain names have been improved.

In addition, we can also access the corresponding Dapp through the wallet application.

When we talk about decentralized domain names, we are mostly talking about ENS domain names. We can understand the ENS domain name as a simplified version of the Ethereum wallet address, which can be easily remembered, and its counterpart is the DNS domain name. Previously, the traditional Internet also completed information simplification through DNS domain names-now whenever we want to visit Google, we only need to enter google.com. ENS domain names often end in .eth.

In addition to Ethereum's ENS, the Bonfida protocol of the emerging public chain Solana also launched a decentralized domain name service. The Bonfida domain name ends in .sol. Bonfida supports linking domain names with data on the chain. Websites hosted in IPFS or Arweave can be completely decentralized by using Solana domain names.

Through the above combination, we can access decentralized DeFi applications in a completely decentralized way, without being affected by regulatory agencies.