-
Notifications
You must be signed in to change notification settings - Fork 849
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
Pinto Yield Adapter #1711
Pinto Yield Adapter #1711
Conversation
The pinto adapter exports pools: Test Suites: 1 passed, 1 total
|
gm,
|
gm @slasher125 , I have just removed it |
The pinto adapter exports pools: Test Suites: 1 passed, 1 total
|
for (const bean of poolData.beans) { | ||
|
||
// Get apy info | ||
const apy = await axios.post(API, { |
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.
whats the reason not fetching from the chain?
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.
Pinto displays a variable apy based on a forward-looking simulation with various inputs of past 30d performance. These values are not stored or computed on chain (it would consume too much gas).
My understanding was that external calls are acceptable for yield-server
The pinto adapter exports pools: Test Suites: 1 passed, 1 total
|
* Pinto Silo yields * Update subgraph query * Remove apyBase 0
Adapter for getting current yields on whitelisted Pinto assets