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
I checked there isn't already an issue for the bug I encountered.
Viem Version
2.21.53
Current Behavior
example: cruzdanilo.base.eth is issued on base, and its avatar record value is eip155:8453/erc721:0x9d42b2a07f7c6a0b0b91daecc61cadb33086dd59/3196, which is an nft on the same chain (chain id 8453), owned by the same account.
when calling getEnsAvatar, the ens text record must be resolved on mainnet, but then viem will try to get tokenURI for the specified address, but using the same client (mainnet), so it fails and returns null.
Expected Behavior
there should be a way to resolve ens nft avatars in other chains
Check existing issues
Viem Version
2.21.53
Current Behavior
example:
cruzdanilo.base.eth
is issued on base, and itsavatar
record value iseip155:8453/erc721:0x9d42b2a07f7c6a0b0b91daecc61cadb33086dd59/3196
, which is an nft on the same chain (chain id 8453), owned by the same account.when calling
getEnsAvatar
, the ens text record must be resolved on mainnet, but then viem will try to gettokenURI
for the specified address, but using the same client (mainnet), so it fails and returnsnull
.Expected Behavior
there should be a way to resolve ens nft avatars in other chains
Steps To Reproduce
Link to Minimal Reproducible Example
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: