Skip to content
This repository has been archived by the owner on Oct 14, 2024. It is now read-only.

Configured cointype introspection #19

Open
JorikSchellekens opened this issue Feb 24, 2023 · 1 comment
Open

Configured cointype introspection #19

JorikSchellekens opened this issue Feb 24, 2023 · 1 comment
Assignees

Comments

@JorikSchellekens
Copy link
Collaborator

ENS uses events to identify which cointypes an account configured to decide which cointypes to display on their UI. This is not possible when the information is all off-chain. The solution proposed by @makoto is to have a function on the resolver which returns the cointypes configured and, in this instance, further resolve these types using CCIP. The UI will attempt to use this function in the event that the resolving contract is not the standard one.

@FawadHa1der FawadHa1der self-assigned this Feb 24, 2023
@FawadHa1der
Copy link
Contributor

FawadHa1der commented Mar 1, 2023

@makoto @JorikSchellekens So this does require changing the l2resolver contract to integrate cointype, perhaps writing a new l2resolver contract since Cairo 1 is right around the corner, I will start working on it but it needs more detailed discussion on the solution to inform this implementation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants