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

Add Unstoppable Domains support (.crypto and new ones) #718

Merged
merged 4 commits into from
May 20, 2024

Conversation

mexcool
Copy link
Contributor

@mexcool mexcool commented May 17, 2024

What?

Add support for Unstoppable Domains by adding the events from the Registry contracts. The initial set up was only for .crypto TLD and then they made it for many more. I split into Crypto Name System (CNS) and Unstoppable Name System (UNS).

How?

I used abi-parser to build the table definitions. The new Registry contract for UNS is a proxy contract with the implementation being this.

All contracts are here.

I added all of them under one parent folder/dataset unstoppable_domains and kept same table_name as the contract name. I added a description to the CNS Registry to clarify those are for CNS.

Related PRs (optional)

Analogous PR for Polygon: nansen-ai/evmchain-etl-table-definitions#283

Anything Else?

  1. The contract_address must be the proxy right? even if I used the implementation in the parser.

More info here: https://docs.unstoppabledomains.com/smart-contracts/overview/uns-architecture-overview/#smart-contract-architecture

@mexcool mexcool marked this pull request as draft May 17, 2024 16:12
@mexcool mexcool marked this pull request as ready for review May 17, 2024 16:24
@araa47
Copy link
Collaborator

araa47 commented May 20, 2024

@mexcool , I would restructure this slightly so all the files are within the folder unstopabbledomains or similar based on the entity.

Then you can split between uns/cns based on file names. CnsRegistry and UnsRegistry.

@medvedev1088 medvedev1088 merged commit 03185bd into blockchain-etl:master May 20, 2024
3 checks passed
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

Successfully merging this pull request may close these issues.

3 participants