-
Notifications
You must be signed in to change notification settings - Fork 1k
Oxium Vaults on Sei Network #2147
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
Conversation
|
The oxium adapter exports pools: Test Suites: 1 passed, 1 total |
|
gm @Screpuh |
@slasher125 The main reason we can't get APY directly from on-chain calls is that the data we need isn’t all stored or derivable from chain. For these vaults, market-making performance depends on orderbook fills that happen across many transactions over time. To calculate APY properly, we have to look at historical fills, compute realized/unrealized pnl, and apply time-weighted returns and prices, which requires aggregating data off-chain. Secondly, part of the vault’s idle liquidity is deployed into staking protocols, so yield comes from multiple sources. Some of that data (like staking rewards) is provided through third-party integrations rather than directly from on-chain contracts,. |
|
The oxium adapter exports pools: Test Suites: 1 passed, 1 total |
Oxium vaults use on-chain orderbook market making strategies, which makes it difficult to calculate APY directly from on-chain data alone. The data is spread across multiple transactions, protocols, and off-chain data over time, so we use our own indexing API to handle this complexity.
Why we use our indexing API
We run an hourly snapshot service that: