-
Notifications
You must be signed in to change notification settings - Fork 3
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
Marinade ez pool lp actions #768
Conversation
092a86c
to
7346be3
Compare
{% endif %} | ||
{% endfor %} | ||
), | ||
token_prices AS ( |
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.
I always debate on how to best handle late arriving prices. Do you think we should try to look at any prices that arrived after the late run?
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.
maybe not a solve for today given the timeline, more curious your thoughts
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.
hmm good point. What is the expected window for token X at time Y to have a price in our table? up to 24 hours?
7fc6531
to
784cdc5
Compare
marinade__ez_liquidity_pool_actions
to surfacedeposit
andwithdraw
events for all pools that use either MSOL or MNDE as one of the LP pairsmarinade__meteora_pivot
andmarinade__meteora_dlmm_pivot
dbt build -s marinade__meteora_dlmm_pivot -t dev
dbt build -s marinade__meteora_pivot -t dev
dbt build -s marinade__ez_liquidity_pool_actions -t dev --full-refresh
dbt build -s marinade__ez_liquidity_pool_actions -t dev