If you carefully analyze the Layer 2 integrated gameplay provided by @ensdomains, you can understand Vitalik's intention: to further shrink Ethereum's DA control over Layer 2 . Why? Next, let me briefly analyze:
The ENS domain name service will define a set of interaction logic. Users only need to enter a short domain name to automatically connect to the associated long address corresponding to the ENS smart contract, which solves the pain point of EOA addresses being complex, difficult to remember and difficult to identify.
It should be said that ENS's domain name service is more aimed at the future expansion market with larger user traffic, especially some Mass Adoption user groups . Layer 2 is the future for Ethereum to expand and absorb large traffic. If ENS's domain name resolution solution cannot cover Layer 2 and only stays at the Ethereum main network level, it will be difficult to open up space for imagination.
Based on this background, ENS will naturally consider providing a complete set of data parsing solutions for Layer 2, allowing users to directly perform domain name resolution and data search on Layer 2, reducing their dependence on their respective Layer 2 decentralized gateways.
In short, this solution allows users to use ENS domain names on various Layer 2 in a secure and decentralized manner.
How to do it?
1) ENS has designed a "Layer Bridge" with interopeablity and interactive communication capabilities, so that each Layer2 can retrieve and effectively verify the domain name data of the Ethereum main network from the off-chain environment. Through this bridging mechanism, the domain name data resolution functions of each layer2 and the mainnet are opened, and ENS short domain names can be used safely on Layer2.
2) EIP3668 mentioned in the document will ensure that the domain name used on the Layer 2 chain can be correctly verified by the mainnet smart contract to prevent the domain name from being misused; while EIP5599 relaxes the original restriction that the domain name must interact with the ENS smart contract to resolve the task. It can be delegated to an external system for processing (Rollup contract), which greatly enhances the parallel processing capability of domain name resolution.
It is not difficult to see that for users to use the ENS domain name normally on layer 2, the prerequisite is to call and verify the global data on the Ethereum mainnet.
This means that to enjoy ENS's set of services, you must use the orthodox Ethereum Data Availability capabilities, and those Layer 2s that are based on OP Stack's hair chain shortcut and place DA on third-party DA platforms such as Celestia are not compatible with ENS.
At this point, it is not difficult to understand Vitalik's intention. I have analyzed in many articles before that after the Cancun upgrade, Layer 2 will definitely usher in a big explosion, and various types of Layer 2 will spring up like mushrooms after a rain. The modular idea and various Stack component services are breaking the mainnet to provide DA. +Layer2 provides extended bounds.
Facing the out-of-control Layer 2 territory, Vitalik will try his best to maintain the legitimacy of the Ethereum mainnet DA. His previous call for Plasma+ZK was a battle to defend the legitimacy of DA. This time, he is promoting ENS's Layer 2 domain name data plan in a high-profile manner. The intention is no different.
Because only DA data is on the Ethereum mainnet, Ethereum Validators can control the "security" of Layer 2 assets. If Validators lose verification control, Ethereum becomes a "bulletin board" for Layer 2 to publish results, and the Layer 2 chain's dependence on Ethereum will also weaken. To a certain extent, it is unclear whether these Layer 2 platforms are still willing to be the Layer 2 of Ethereum. . Therefore, Vitalik will do everything possible to keep the development trajectory of Layer 2 on the path of Ethereum’s legitimacy.
If you look closely, the Crypto world has always been very political.
Of course, ENS is regarded by Vitalik as the most successful non-financial application on Ethereum. In addition, ENS can indeed bring a user-friendly experience to the blockchain after Mass Adoption, which is in line with Layer 2 and will expand to a wider range of web3 people in the future. scale goals.
In short, using ENS to define a set of interoperability specifications for Layer 2 platforms and at the same time tightening DA control is a great move!
