initiate eigenlayer project, models and sources

[bowenli86]

Description:

• initiate eigenlayer project and eigenlayer source
• add several models, covering
  • tvl
  • inflow/outflow
  • tvd
  • avs
  • operator
  • rewards v1
  • programmatic incentive
  • strategies

---

quick links for more information:

• README.md
• spellbook docs
• CONTRIBUTING.md

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[bowenli86]

I have read the CLA Document and I hereby sign the CLA

[bowenli86]

@jeff-dude @0xBoxer @0xRobin

[0xRobin]

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)?

[bowenli86]

@0xRobin thank you

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?

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

What data do they currently have available (and thus what gap are we trying to fill with the spell)?

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

[bowenli86]

@0xRobin thank you for the approval!

does the workflow also need to be approved? i can't seem to merge without it passing and it's been pending

[jeff-dude]

only us as maintainers can approve and run workflows. this typically only happens on first time contributor PRs. moving forward, you shouldn't hit that block. as for merging, that will also only fall on maintainers.

i will give a final review and prep for merge shortly.

[jeff-dude]

thank you for the patience. i have pushed a few commits, to try to help expedite. these are mostly best practice items / reusing new utils tables for time series.

• use _projects directory, to help keep eigenlayer models near the top and easier to find. most below that are not in this directory are legacy and we just haven't taken time to clean / organize completely
• use blockchain in schema names, then corresponding changes to files to match. these are all ethereum, so using that chain name. this also allows flexibility in the future to add other chains without naming conflict
• as mentioned, use new utils.days rather than rebuild yourself

[bowenli86]

thank you for the patience. i have pushed a few commits, to try to help expedite. these are mostly best practice items / reusing new utils tables for time series.

• use _projects directory, to help keep eigenlayer models near the top and easier to find. most below that are not in this directory are legacy and we just haven't taken time to clean / organize completely
• use blockchain in schema names, then corresponding changes to files to match. these are all ethereum, so using that chain name. this also allows flexibility in the future to add other chains without naming conflict
• as mentioned, use new utils.days rather than rebuild yourself

make sense, thanks!

[jeff-dude]

okay, this all looks good to me. can you do me a favor, and query all 15 views built in CI process here on dune app, ensure you are happy with results?

[jeff-dude]

also, minor note, i don't think the order by in view definitions will do anything. you can test while querying CI views if you want, but you most likely need to use the order by on the queries directly downstream

[bowenli86]

@jeff-dude tried, fixed a casting issue, made a couple into tables as they seem very expensive to query repeatedly, but feel free to revert if you disagree

[jeff-dude]

@jeff-dude tried, fixed a casting issue, made a couple into tables as they seem very expensive to query repeatedly, but feel free to revert if you disagree

those changes work for me. if you're good, then i'm good. keep in mind, if these tables really grow, it would be good to consider making them incremental instead. right now, they are small enough to build quickly on full history each time. let's keep this in mind as you continue to build in future PRs.

[bowenli86]

@jeff-dude tried, fixed a casting issue, made a couple into tables as they seem very expensive to query repeatedly, but feel free to revert if you disagree

those changes work for me. if you're good, then i'm good. keep in mind, if these tables really grow, it would be good to consider making them incremental instead. right now, they are small enough to build quickly on full history each time. let's keep this in mind as you continue to build in future PRs.

sounds good, thank you!

[bowenli86]

@jeff-dude lmk if this can be merged today

[gitpoap-bot]

Congrats, your important contribution to this open-source project has earned you a GitPOAP!

GitPOAP: 2025 Dune Contributor:

Head to gitpoap.io & connect your GitHub account to mint!

Learn more about GitPOAPs here.