Alw joe v2 data

[alexwes]

PR Objectives:

• Create an ez_metrics table that can be used in the outerlands index so as to not require additional logic to handle ez_metrics_by_chain
• Add all of the Trader Joe v2.0, 2.1, 2.2 metrics to the pipeline

Outcome:

• ez_metrics table is created, and works with the outerlands index logic, and has all versions data
• 'ez_metrics_by_chain' largely unchanged (added some coalesce)
• ez_metrics_by_chain does not include v2.0, 2.1, 2.2 data as we were missing v2.0, 2.1, 2.2 TVL by chain. Adding the rest of the v2+ metrics (dau, txns, fees) but not TVL would have resulted in a more confusing experience for the end user, especially Snowflake Share users and users of the sectors dashboard. Defillama does support TVL data for these protocol versions, but does not offer a 'by chain' breakdown, making it impossible to add to the ez_metrics_by_chain.

Next steps would be to get Trader Joe TVL for v2+.

daily_trader_joe_job runs successfully, materializing ez_metrics + by_chain tables.

[SebMelendez01]

One change

[SebMelendez01]

Can add a comment in the ez_metrics... about the differences in the ez_metrics_by_chain and the ez_metrics model. If I remember from our convo ez_metrics_by_chain does not include the v2 or greater data?

can you also add a note in ez_dex_swaps?

[alexwes]

Converting this PR to draft.

Reasoning goes as follows:

1. Realized the barn.traderjoexyz.com API was returning an error
2. Turns out you can only pull data in 180 intervals
3. This led me to rewrite the API extraction logic
4. We were pulling data from the API for what we believed to be v2.0 of the protocol.
5. On validating the data I realized that the API data looked very similar to the onchain data we had pulled for v2.1 and v2.2
6. After playing around with the data with Kyle for a bit we realized it was the exact same!
7. Learning: The API rolls up v2.1 + v2.2 into one endpoint.
8. Defillama also leverages TheGraph to pull v2.0 data it seems (Github)

We also learned that v2.0 Factory contract address has been made publicly available in the docs. This was new.

Next steps are to remove the API extract logic and pull the data for v2.0 from the chain.