ENS Resolver

The objective was to create something similar to https://github.com/ensdomains/offchain-resolver but using Scaffold-ETH 2 (https://github.com/scaffold-eth/scaffold-eth-2), using next.js as an off-chain resolver gateway and the ens data (addresses, text records, content-hash) saved at a Redis database. Then, having this working locally I wanted to deploy the resolver contract to mainnet to be able to create a free name server for BuidlGuidl members (I'm a BG member), using a subname from buildguidl.eth. To test it, I deployed the resolver contract at https://etherscan.io/address/0xd4b3fc529e71093f4ffb23a8a84da247dd1a8fe2 (Verified Contract) and tried to resolve some sub-names using my test.damianmarti.eth ens name. I saved two subnames (damu.test.damianmarti.eth and ens.test.damianmarti.eth). When I use a name resolver, the off-chain gateway is called, and the gateway resolves the name successfully, but then I get the 0x0000000000000000000000000000000000000020 address. It seems like the response is not the expected or maybe the signature is not valid, but this was working locally using the ENS client from the first repository.I will keep debugging it or ask for help from the ENS devs.

The ENS off-chain resolver gateway was migrated to Scaffold-ETH2 using next.js and saving the data to a Redis database. This is a project based on ENS, trying to develop more options to implement an off-chain resolver, so other developers can use it. Ethers.js library is used to contract, abi, encode, decode, and this kind of stuff.