Implement table definition files for ENS events about ethereum-etl-airflow

[medvedev1088]

Ok turns out there is no single PublicResolver, instead a resolver per each domain in the Registry as explained here https://docs.ens.domains/#ens-architecture. Can we instead map the top ENS addresses (by number of txns) listed on Etherscan https://etherscan.io/accounts/label/ens, i.e. 0x6090a6e47849629b7245dfa1ca21d94cd15878ef, 0x314159265dd8dbb310642f98f50c066173c1259b, 0xf0ad5cad05e10572efceb849f6ff0c68f9700455, 0x1da022710df5002339274aadee8d58218e9d6ab5, 0x9062c0a6dbd6108336bcbe4593a3d1ce05512069?

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 500.0 DAI (500.0 USD @ $1.0/DAI) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $150,718.76 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 2 weeks from now.
Please review their action plans below:

1) igetgames has applied to start work (Funders only: approve worker | reject worker).

I will implement the DAG according to the referenced issue (ethereum-etl-airflow/issues#17).
2) askeluv has started work.

Similarly to the bounty for parsing 0x events, I'll use the separately created DAG builder to generate an Airflow DAG which parses ENS events from Ethereum logs. Will include the contracts mentioned in the task and their respective ABIs.

Learn more on the Gitcoin Issue Details page.

[askeluv]

Using Etherscan, I was able to map the two first contracts, but not the last:

ENS -> 0x314159265dd8dbb310642f98f50c066173c1259b
ReverseRegistrar -> 0x9062c0a6dbd6108336bcbe4593a3d1ce05512069
PublicResolver -> ?

Any pointers on how to find the PublicResolver contract?

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 500.0 DAI (500.0 USD @ $1.0/DAI) has been submitted by:

1. @askeluv

@ceresstation please take a look at the submitted work:

• PR by @askeluv

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $152,094.30 more funded OSS Work available on the Gitcoin Issue Explorer

[askeluv]

Already did 0x314159265dd8dbb310642f98f50c066173c1259b in #20 @medvedev1088

Will spin up a separate PR for the following:
0x6090a6e47849629b7245dfa1ca21d94cd15878ef
0xf0ad5cad05e10572efceb849f6ff0c68f9700455
0x1da022710df5002339274aadee8d58218e9d6ab5 0x9062c0a6dbd6108336bcbe4593a3d1ce05512069

[askeluv]

It turns out 0x9062c0a6dbd6108336bcbe4593a3d1ce05512069 does not have any events.

But I've added table definitions for the rest in this PR: #22

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 500.0 DAI (500.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @askeluv.

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $151,533.53 more funded OSS Work available on the Gitcoin Issue Explorer