I’m pleased to announce that we have the first version of an implementation of ENS offchain resolution (ENSIP 10 + EIP 3668) now ready for testing by developers.
The offchain resolver is a starter-kit for building infrastructure to resolve ENS names using external services. This implementation defaults to using a backend that loads names from a JSON flatfile, but the backend is easily pluggable and can be replaced to source records from any database as needed.
Over the next few days I will be improving the documentation and tooling, but for now the root level README describes how to try it out for yourself in a test environment.
This is an important first step to ENS-on-L2; once resolution support is available in ENS, it enables wallet providers etc to provide subdomains to their users at low-to-no cost by storing the records offchain and relying on messages signed using a trusted key for verification.
The next step from here will be to make this more production-ready, and to begin developing gateway and resolver implementations that support other verification methods - specifically, verifying proofs from layer 2 networks, which will make storing ENS names on L2s like Optimism and Arbitrum possible without any additional trust assumptions. This will make it possible for individual users to migrate their names to L2s.