Steve
@stevedylandev.eth
So close 🥲
3 replies
0 recast
23 reactions
Greg
@greg
😮💨😮💨 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
2 replies
0 recast
10 reactions
Steve
@stevedylandev.eth
wait wait wait, you're telling me I can use this instead of CCIP? 👀
2 replies
0 recast
1 reaction
Steve
@stevedylandev.eth
I think I just answered my own question? lol
3 replies
0 recast
1 reaction
Pedro Santana
@z0uk
You actually building the neofetch wallet.
1 reply
0 recast
2 reactions
Greg
@greg
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)
0 reply
0 recast
3 reactions
v1rtl
@v1rtl.eth
I'm actually working on UniversalResolver support for ensjs, if you're curious you can check this PR, specifically this file: https://github.com/ensdomains/ensjs/blob/159e7b9f16160164c79ba71e6491e09cd5c7ab44/packages/ensjs/src/actions/public/resolveNameData.ts tldr; you send a multicall request of an array of ABI encoded function calls to UR, then get a multicall response back and decode it using the same ABIs, in case you want to resolve multiple records at the same time
0 reply
0 recast
1 reaction
