😮‍💨😮‍💨

i started a new guide that should make first part easier! https://github.com/ensdomains/docs/pull/445

and lmk if you have any questions about ccip read, i can help walk you through it

DX Engineer | DevRel at OpenZeppelin | Building orbiter.host | stevedylan.dev/links | opinions are my own

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs

wait wait wait, you're telling me I can use this instead of CCIP? 👀

I think I just answered my own question? lol

checksum the addresses before comparing at the end! or maybe lowercase both, i forget the correct way off hand. looks like they are equal though - just one is bytes and the other is address

in a case where forward & reverse resolution dont match in a primary name lookup, you should return null (this is handled internally by the universal resolver’s reverse() method, it’ll throw an error so you don’t need to verify in client code)

Ahhh ok, that makes sense. Good to know though! Will use that instead of the normal flow.

not quite - the universal resolver just simplifies the path to getting there

CCIP Read isn’t needed for names where all the data is on L1, like yours, but is needed for stuff like *.base.eth

Try greg.base.eth as a test

resolve() will revert with OffchainLookup and your code should handle that

I think i wrote in there somehwhere that the guide is written for library devs and assumes they already support CCIP Read at a lower level