Add Aave to contract parser

[askeluv]

Context

We add "table definition" for contract events so that we can regularly parse these events from Ethereum logs. One benefit of this is that the events become available in public BigQuery tables, under the blockchain-etl project.

For more details on this, please read How to get any Ethereum smart contract into BigQuery.

In this ticket we are looking to add datasets for Aave.

Proposed solution

Add table definition files for Aave by following the checklist below.

Checklist

1. 1. Identify all smart contracts for Aave
2. 2. Generate table definition files for all the contracts in your list using this Contract Parser
3. 3. Create Pull Request containing all the table definition files

Please note

• For step 1 you could use a site like DappRadar or ETH Gas Station to find the contracts.
• For step 2 that you may have to manually edit the table definition files if there are multiple contracts with the same name. You can add e.g. _v2 so contract becomes contract_v2.

Before applying for this bounty, please list the contracts identified in step 1, and confirm you've understood the process.

It may be helpful to look at past PRs that are labeled contract parsing.

[sebastiantf]

Would love to work on this

[askeluv]

Cool @sebastiantf - I'm waiting for the Gitcoin transaction to go through. There will be a $20 USDC bounty on this.

[gitcoinbot]

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

---

This issue now has a funding of 20.0 USDC (20.02 USD @ $1.0/USDC) 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
• $133,982.47 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 1 month from now.
Please review their action plans below:

1) sebastiantf has been approved to start work.

Easy task. Can turn around fast

Learn more on the Gitcoin Issue Details page.

[sebastiantf]

Hey I'm seeing the same contract name AToken in about 6+ contracts with the same events. So I'm renaming them with suffixes like _v2.json, _v3.json, ... _v7.json. Is that normal?

[gitcoinbot]

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

---

Work for 20.0 USDC (20.01 USD @ $1.0/USDC) has been submitted by:

1. @sebastiantf

@askeluv please take a look at the submitted work:

• PR by @sebastiantf

---

• 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
• $133,695.63 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

⚡️ A tip worth 20.00000 USDC (20.02 USD @ $1.0/USDC) has been granted to @sebastiantf for this issue from @askeluv. ⚡️

Nice work @sebastiantf! Your tip has automatically been deposited in the ETH address we have on file.

• $137566.85 in Funded OSS Work Available at: https://gitcoin.co/explorer
• Incentivize contributions to your repo: Send a Tip or Fund a PR
• No Email? Get help on the Gitcoin Slack

[gitcoinbot]

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

---

The funding of 20.0 USDC (20.02 USD @ $1.0/USDC) attached to this issue has been approved & issued to @sebastiantf.

Additional Tips for this Bounty:

• askeluv tipped 20.0000 USDC worth 20.02 USD to sebastiantf.

---

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