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
Because resolving ENS names requires heavy packages for unicode normalization, we should first enable ENS resolution in this package by connecting to a resolver endpoint via fetch.
This comes with many trade-offs, so consider this a temporary solution.
The primary trade-off is that using ENS resolution in this package would require a constant public internet connection. Previously a user of this package could be referencing their own eth node offline with no issues.
This is a temporary solution until normalization packages can be reduced in-size upstream via #144
The text was updated successfully, but these errors were encountered:
TLDR: Just do a fetch to this for now https://api.ensideas.com/ens/resolve/daws.eth
Because resolving ENS names requires heavy packages for unicode normalization, we should first enable ENS resolution in this package by connecting to a resolver endpoint via fetch.
This comes with many trade-offs, so consider this a temporary solution.
The primary trade-off is that using ENS resolution in this package would require a constant public internet connection. Previously a user of this package could be referencing their own eth node offline with no issues.
This is a temporary solution until normalization packages can be reduced in-size upstream via #144
The text was updated successfully, but these errors were encountered: