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 contract parsers for SushiSwap #134

Open
3 tasks
askeluv opened this issue Aug 28, 2020 · 6 comments
Open
3 tasks

Add contract parsers for SushiSwap #134

askeluv opened this issue Aug 28, 2020 · 6 comments

Comments

@askeluv
Copy link
Member

askeluv commented Aug 28, 2020

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 SushiSwap.

Proposed solution

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

Checklist

  1. 1. Identify all smart contracts for the 13 farms listed on https://app.sushiswap.org/farms
  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 2 that you may have to manually edit the table definition files if there are multiple contracts with the same name. If they have the same name, add the relevant token, e.g. _YFI.

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
Copy link
Contributor

@askeluv It seems staking to all the 13 pools are facilitated by the single MasterChef contract at 0xc2edad668740f1aa35e4d8f227fb8e17dca888cd. I got the info from their discord.

I shall create a PR with the table definition files for that contract. Is that good?

@askeluv
Copy link
Member Author

askeluv commented Aug 28, 2020

@sebastiantf thanks for checking! yeah that sounds good, as long as it has the basic events like Withdrawn and Staked.

@sebastiantf
Copy link
Contributor

These are the events found from using the Contract Parser:

Screenshot 2020-08-28 at 2 55 27 PM

@askeluv
Copy link
Member Author

askeluv commented Aug 28, 2020

Perfect, let's do it :)

@sebastiantf
Copy link
Contributor

@askeluv I have a PR up at #135

@sebastiantf
Copy link
Contributor

@askeluv I have submitted work on Gitcoin

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

No branches or pull requests

2 participants