-
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
Celo Mento Protocol trades #4413
Conversation
Workflow run id 6290937343 approved. |
Workflow run id 6290937357 approved. |
Workflow run id 6301154159 approved. |
Workflow run id 6301154240 approved. |
Workflow run id 6301201432 approved. |
Workflow run id 6301201218 approved. |
Workflow run id 6301302269 approved. |
Workflow run id 6301302341 approved. |
Workflow run id 6301582904 approved. |
Workflow run id 6301583123 approved. |
Workflow run id 6302060948 approved. |
Workflow run id 6302061021 approved. |
Workflow run id 6302152615 approved. |
Workflow run id 6302152743 approved. |
Workflow run id 6302186809 approved. |
Workflow run id 6302186885 approved. |
Workflow run id 6310528458 approved. |
Workflow run id 6310528635 approved. |
Workflow run id 6311087439 approved. |
yes, adding to
agreed! will remove tokens erc20 refs and bring pool models to follow |
Workflow run id 6864368405 approved. |
Workflow run id 6864368552 approved. |
Workflow run id 6865783322 approved. |
Workflow run id 6865783518 approved. |
Workflow run id 6865808669 approved. |
Workflow run id 6865808959 approved. |
pools updated now
on that last bit - exciting stuff! but does it mean my #4762 doesn't have a chance to get in before new magic starts flowing? |
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.
few comments below
also, this shouldn't happen in this PR, but seems like dex.pools
is a nice candidate for a redesign like dex.trades
-- should be a bit easier to do, on number of models alone
ref('mento_celo_pools_v1'), | ||
ref('mento_celo_pools_v2') |
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.
similar to dex.trades
lineage, should these be named as below?
mento_v1_celo_pools
mento_v2_celo_pools
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.
would mean changes to file names, config settings, refs, etc etc
select | ||
'celo' as blockchain, | ||
'mento' as project, | ||
'v1' as version, |
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.
can you do me a favor and double check the usage of version
in other dex pool models? do they preface with v
in front of the version number?
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.
Sure, looks like most pool models don't use 'v' prefix - only uniswap models do (fix in a separate pr?).
I'll remove 'v' for Mento.
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.
yeah, we can fix in later PR for others, no worries
config( | ||
schema = 'mento_celo', | ||
alias = 'pools_v1', | ||
materialized = 'table' |
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.
any reason v1 is full table refresh each time, while v2 is 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.
v1 is static, new pools won't get added, while v2 get updated from time to time (not too often tho).
I wasn't aware that table materialization gets refreshed every time - any better option to use here?
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.
the combo of materialized = 'table'
and tags = ['static']
will do the trick
we set up our orchestration to exclude anything static
, so they only run when modified on main branch
nope, these will continue until that work is final. it's in a PoC phase at the moment. i'll get it merged soon 🤝 |
Workflow run id 6866742695 approved. |
Workflow run id 6866742670 approved. |
@hildobby do you want to take it over as you were the one who created dex.pools originally? |
no rush here. if not prioritized, dune team will get to it eventually. just focusing on most commonly used ones first |
Workflow run id 6867014031 approved. |
Workflow run id 6867014199 approved. |
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.
looks good -- thank you!
fyi @Hosuke |
Aim: add Mento Protocol to dex.trades