Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create ENS resolver in a public endpoint. Connect resolveName to this with a fetch #143

Open
dawsbot opened this issue Jun 5, 2022 · 0 comments

Comments

@dawsbot
Copy link
Owner

dawsbot commented Jun 5, 2022

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

@dawsbot dawsbot self-assigned this Jun 5, 2022
@dawsbot dawsbot removed their assignment Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant