-
Notifications
You must be signed in to change notification settings - Fork 1k
APY adapter for avUSD, avBTC and avETH #2163
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
|
Error while running avant-protocol adapter: Test Suites: 1 failed, 1 total |
|
@spider-g sir u'll need to use the individual child adapter protocol name(s) which is why the tests are failing |
|
Error while running avant-protocol adapter: Test Suites: 1 failed, 1 total |
|
I have updated the project slugs, the one that seems to be still missing is avant-aveth which should have already been imported by the PR DefiLlama/DefiLlama-Adapters#16776 |
|
@spider-g sry i think i wasn't clear enough: the project field must be constant (see the test output, best to run this locally btw) and it must match the file name. so, in your case, u'd need to list 3 separate adapters (u can export from one so we dont duplicate the same code N times). |
|
The avant-avbtc adapter exports pools: Test Suites: 1 passed, 1 total |
|
The avant-avbtc adapter exports pools: Test Suites: 1 passed, 1 total |
|
@spider-g any reason why the apy values are quite diffrent compared to ur ui? |
Great question. Yes, the methods are different: on our UI, we look at the amount of rewards that will be sent to vault stakers today (distribution is daily), so users get a sense of their yield if they enter the protocol at that moment — the logic is therefore forward-looking. The DefiLlama adapter, on the other hand, looks at rewards distributed over the past week and then prorates them to calculate the APY, so it’s historical. |
No description provided.