-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
initiate eigenlayer project and eigenlayer source, add v2_withdrawal_queued_flattened data model #7622
base: main
Are you sure you want to change the base?
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
…queued_flattened data model
3f1b813
to
6bc5a59
Compare
JSON_PARSE(withdrawal) AS parsed_withdrawal | ||
FROM | ||
{{ source('eigenlayer_ethereum', 'DelegationManager_evt_WithdrawalQueued') }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May be incremental?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @bowenli86, thanks for starting to build on spellbook! Very exciting to have some official EigenLayer eyes on this.
We will need some more context on your vision so we can help you further.
Ideally we build the end spells as simple generic tables that are able to serve a multitude of wizards needs.
- What end goal tables do you have in mind to expose as a spell?
- What's your usecase for needing these tables, what are some other example usecases that wizards will be able to use the spells for?
- What data do they currently have available (and thus what gap are we trying to fill with the spell)?
@0xRobin thank you
none of Eigenlayer TVL boards on Dune right now are correct, b/c the calculation needs complex processing by joining multiple events, and decipher them correctly, etc for the first phase, we will expose a few key metrics like TVL, operator<>AVS relationships, and rewards. I will decode events (bronze) and add static data to Dune, build several intermediary (silver) tables, and final gold tables for TVL, operator<>AVS relationships, and rewards wizards can build more analysis on top of these bronze, silver and gold tables
gaps as mentioned above. all tables i add to dune will fill the gap eg. flattening withdrawalqueued events as a table is first step to decipher events to correct bronze tables which will contribute to futher development on top |
dd6a144
to
2748aba
Compare
Description:
quick links for more information: