crosschain-resolver

@ensdomains/crosschain-resolver

A l1 resolver contract that is built on top of evm-verifier and verify l2 data.

Deployment

Pior to deploying ENS gateway contracts, deploy your own EVM Gateway verifier and host the gateway, or use the preexising ones(OP, Base, Arbitrum ).

Once EVM verifier contracts are deployed, create .env and set the following variables (use VERIFIER_ADDRESS to specify the chain specific verifier)

• DEPLOYER_PRIVATE_KEY
• L1_PROVIDER_URL
• L2_PROVIDER_URL
• L1_ETHERSCAN_API_KEY
• VERIFIER_ADDRESS = Address deployed via -verifier repo on evmgateway
• ENS_ADDRESS = ENS Registry address
• WRAPPER_ADDRESS = ENS Wrapper address
• L2_GRAPHQL_URL = Deploy subgraph with ens-l2-delegatable-resolver-subgraph

bun run hardhat deploy --network sepolia

Deployed addresses

OP on Sepolia

L2

• DelegatableResolver = 0x017845E4518dB01EFCAFd7Acb192aF924B432d66 = this is used as a template so cannot interact directly
• DelegatableResolverFactory = 0x79b784075600c5C420aC3CEd45f04EEA50306a96

L1

• OPVerifier = 0x0e8DA38565915B7e74e2d78F80ba1BF815F34116
• L1Resolver = 0x57C1f50093C1017AE81EBAF336511ACcc48061e2 = Currently op.evmgateway.eth is set to the resolver

Base on Sepolia

L2

• DelegatableResolver = 0xd8A6B88b0a0B419fCce6cfBD60F21f1b7761eeB2 = this is used as a template so cannot interact directly
• DelegatableResolverFactory = 0xCcFC8Be7f65E1D46Af71cf6C06668DDA25f51e3e

L1

• OPVerifier = 0xAdef74372444e716C0473dEe1F9Cb3108EFa3818
• L1Resolver = 0xF6EfB10e47d6D4C1023BBFa5e6396B00915FbD41 = Currently base.evmgateway.eth is set to the resolver

Arbitrum on Sepolia

L2

• DelegatableResolver = 0xCcFC8Be7f65E1D46Af71cf6C06668DDA25f51e3e this is used as a template so cannot interact directly
• DelegatableResolverFactory = 0xF2c102E96A183fC598d83fDccF4e30cfE83aedCd

L1

• ArbVerifier = 0x6820E47CED34D6F275c6d26C3876D48B2c1fdf27
• L1Resolver = 0xA47b9B72571e23604f067dfd4F22785c33E9cF9c = Currently arb.evmgateway.eth is set to the resolver

Usage

Move resolver to L2

Before starting, deploy L2ResolverFactory

Once deployed, set the l1 resolver to the name, derive l2 resolver address using DelegatableResolverFactory.predictAddress, then set it as a target

// On L1
await ENS.setResolver(l1lresolver)
const l2resolverAddress = await DelegatableResolverFactory.predictAddress(OWNER_ADDRESS)
await L1Resolver.setTarget(encodedname, l2resolverAddress)
// On L2
const l2resolverAddress = await DelegatableResolverFactory.predictAddress(OWNER_ADDRESS)
await DelegatableResolverFactory.create(OWNER_ADDRESS)
await DelegatableResolver['setAddr(bytes32,address)'](node, OWNER_ADDRESS)
// On L1
const abi = [
  "function addr(bytes32) view returns (address)",
  "function resolve(bytes,bytes) view returns (bytes)",
]
const i = new ethers.Interface(abi)
const calldata = i.encodeFunctionData("addr", [node])
const result2 = await l1resolver.resolve(encodedname, calldata, { enableCcipRead: true })
const address = i.decodeFunctionResult("addr", result2)[0]

NOTE: The l1 resolver must be queried through resolve function to handle subnames

Using the scripts

DEPLOYER_PRIVATE_KEY=$DEPLOYER_PRIVATE_KEY L1_PROVIDER_URL=$L1_PROVIDER_URL L2_PROVIDER_URL=$L2_PROVIDER_URL L1_ETHERSCAN_API_KEY=$L1_ETHERSCAN_API_KEY L2_ETHERSCAN_API_KEY=$L2_ETHERSCAN_API_KEY L2_PROVIDER_URL=$L2_PROVIDER_URL L2_RESOLVER_FACTORY_ADDRESS=$L2_RESOLVER_FACTORY_ADDRESS L1_RESOLVER_ADDRESS=$L1_RESOLVER_ADDRESS ENS_NAME=$ENS_NAME yarn setupl1

DEPLOYER_PRIVATE_KEY=$DEPLOYER_PRIVATE_KEY L1_PROVIDER_URL=$L1_PROVIDER_URL L2_PROVIDER_URL=$L2_PROVIDER_URL L1_ETHERSCAN_API_KEY=$L1_ETHERSCAN_API_KEY L2_ETHERSCAN_API_KEY=$L2_ETHERSCAN_API_KEY L2_PROVIDER_URL=$L2_PROVIDER_URL L2_RESOLVER_FACTORY_ADDRESS=$L2_RESOLVER_FACTORY_ADDRESS ENS_NAME=$ENS_NAME yarn setupl2 --network optimismSepolia/baseSepolia/arbitrumSepolia

L1_PROVIDER_URL=$L1_PROVIDER_URL L1_ETHERSCAN_API_KEY=$L1_ETHERSCAN_API_KEY L2_ETHERSCAN_API_KEY=$L2_ETHERSCAN_API_KEY L2_PROVIDER_URL=$L2_PROVIDER_URL  ENS_NAME=$ENS_NAME yarn getaddr

Issue subname to L2

Assuming you have already moved the parent name to a l2, approve subname to a user (aka operator)

// On L2
const OPERATOR_ADDRESS = ''
const PARENT_NAME = 'op.evmgateway.eth'
const SUBNAME = `${SUBNAME}.${PARENT_NAME}`
const l2resolverAddress = await DelegatableResolverFactory.predictAddress(OWNER_ADDRESS)
const DelegatableResolver = new ethers.Contract(l2resolverAddress, abi, l2provider);
await DelegatableResolver.approve(encodedname, OWNER_ADDRESS, true)

Using the script

OPERATOR_ADDRESS=$OPERATOR_ADDRESS DEPLOYER_PRIVATE_KEY=$DEPLOYER_PRIVATE_KEY L1_PROVIDER_URL=$L1_PROVIDER_URL L2_PROVIDER_URL=$L2_PROVIDER_URL L1_ETHERSCAN_API_KEY=$L1_ETHERSCAN_API_KEY L2_ETHERSCAN_API_KEY=$L2_ETHERSCAN_API_KEY L2_PROVIDER_URL=$L2_PROVIDER_URL L2_RESOLVER_FACTORY_ADDRESS=$L2_RESOLVER_FACTORY_ADDRESS ENS_SUBNAME=$ENS_SUBNAME yarn approve --network optimismSepolia/baseSepolia/arbSepolia

Once done, set addrss of the subname from the operator, wait 10~20 min (depending on the duration of l2 chain commiting the latest stateroot into l1), then query the subname on L1