-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
ENS resolver in Trezor Suite #8618
Comments
Good idea. I was looking and the current API of blockbook doesn't have that. Ethereum name service (ENS) operates as a set of smart contracts with two principal components: registry and resolvers. It could be in blockbook but there are also pretty good libraries for that such as wagmi (a collection of React Hooks) that has useEnsResolver hook that could be used for that. Also in ENS Front-End Design Guidelines there is also another recommendation where to use ENS names besides inputs and that is when showing addresses in e. g. transaction history where we can show ENS names instead of almost full address. Yes we can keep both but ENS address can be shown as "primary" there. Happy to be assigned on this. |
We can also add it to transaction history as Blockbook returns those data. It is in It supports only ENS, not unstoppable domains, which we should also consider https://etherscan.io/name-lookup# |
Waiting for trezor/blockbook#1108 |
When user type
something
.eth or .box, Suite will ask Blockbook for the address connected to the name and fill it inside the address field.Usage
The text was updated successfully, but these errors were encountered: