You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
here is feedback on the ENS docs I came up with after building a cross chain resolver on ENS at ETH Singapore. For context, I have good experience with Solidity but it was my first time building with ENS.
The cross-chain resolver flow can be initially intimidating. The docs help to outline the process but some parts lack depth e.g. the following picture is helpful but doesn't mention which network each address belongs to. Which can be quite confusing if you are not familiar with ENS. Are they each on different networks ? all on the same ?
It would also be useful to explain how the mainnet resolver knows which offchain gateway to query when the subdomain does not exist on mainnet (*.name.eth) e.g. It checks the owner of the higher level domain (name.eth) and uses this address to find the associated offchain resolver deployed using ccip.tools for example.
Hopefully this feedback is helpful, let me know if you have any questions.
cheers,
Joe
The text was updated successfully, but these errors were encountered:
Hi ENS team,
here is feedback on the ENS docs I came up with after building a cross chain resolver on ENS at ETH Singapore. For context, I have good experience with Solidity but it was my first time building with ENS.
The cross-chain resolver flow can be initially intimidating. The docs help to outline the process but some parts lack depth e.g. the following picture is helpful but doesn't mention which network each address belongs to. Which can be quite confusing if you are not familiar with ENS. Are they each on different networks ? all on the same ?
It would also be useful to explain how the mainnet resolver knows which offchain gateway to query when the subdomain does not exist on mainnet (*.name.eth) e.g. It checks the owner of the higher level domain (name.eth) and uses this address to find the associated offchain resolver deployed using ccip.tools for example.
Hopefully this feedback is helpful, let me know if you have any questions.
cheers,
Joe
The text was updated successfully, but these errors were encountered: