-
Notifications
You must be signed in to change notification settings - Fork 126
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
Mapping ETH addresses to ENS addresses #40
Comments
You should be able to get this from Bigquery DB: e.g |
So i started working on this. The data referenced here is the forward-lookup, which is not 1:1 with a name. What we need is reverse lookups instead. |
Data is there, i'm just not sure we can use it:
|
I don't think I get the issue, if we have ENS names and their associated addresses can't we just join that to the mev_inspections db? |
there's forward and reverse ENS lookups. obadiaa.eth and alexo.eth could point to 0x12345 . But 0x12345 can only point to one of those names. for the "obadiaa.eth and alexo.eth" , which do we choose? |
The "worst" address has over 1,000 names pointing to it:
|
lol, and has no reverse records |
Ahh I see, thank you 🙏 |
If there's no way to reverse lookup, the next best thing is to only filter for forward lookups associated to a single name? For the addresses with multiple ENSs I wouldn't want to arbitrarily choose which one to use |
Out of the 13,000 records in that csv i extracted, 1,920 are only single-names. |
Is there a list of ENS addresses somewhere we could join in our DB / queries so that some addresses are replaced with their ENS entries?
The text was updated successfully, but these errors were encountered: