gm,
Context
DeWeb offers a decentralized web on the Massa network. Contents are deployed across the entire network, providing more resilience and resistance to censorship.
To access DeWeb, users can install a local server but this requires technical skills (and time). Otherwise, they can go through a provider that offers a centralized gateway to DeWeb, such as *.massa.network.
Website creators can also register a .massa domain name (not an official TLD) to host their site, such as steve.massa. Users can then access the content through a gateway: steve.massa.network.
Challenges
To facilitate massadoption and access to DeWeb, naming systems are essential. The DNS, although its operation is regulated and centralized by several companies, is the reference naming system for over 30 years and will continue to be so for many years.
As a result, I think it’s essential to have a bridge between DNS (Web2) and decentralized networks like Massa DeWeb. Gateway providers are working in this direction.
To move towards interoperability, here are several proposals. I let you judge their relevance and priority. I am also available to discuss these topics further.
Proposals
- Implement the DNSLink standard
DNSLink offers a protocol to link a traditional domain name with IPFS content. It would be possible to implement a solution so that it works the same way with a site on the DeWeb. Thus, site creators could easily configure their personal domain name.
In a second time, company like Fleek.xyz (leader on IPFS hosting) could easily implement DeWeb.
- Import DNS domain names into MNS
Currently MNS only supports .massa domain names which is an extension not recognized by ICANN, and which only works on the Massa network. As proposed by ENS, one could imagine being able to import a DNS domain name into MNS, thanks to DNSSEC signatures. This would allow domain names to be tokenized (RWA narrative).
2.bis. Enable interoperability with ENS
Ethereum Name Service is the leader in on-chain naming systems. Their vision is consistent with Massa’s, operating with a DAO and open source. Thanks to their CCIP Read (EIP-3668), they allow ENS to be used cross-chains. For Massa, this would allow them to benefit from a crypto-universal naming system and all the features it offers (DNS import, SIWE, records, etc.).
3.bonus. Acquire the .massa TLD from ICANN
The next round of new domain name extensions will take place soon. Massa could submit its application to obtain the .massa TLD. Applications are open until the end of the year, but there is a significant cost.