-
Notifications
You must be signed in to change notification settings - Fork 13
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
new aave aprs and default yield fee #1224
Conversation
🦋 Changeset detectedLatest commit: 8d42488 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
const fee = | ||
pool.type === 'META_STABLE' | ||
? parseFloat(pool.dynamicData.protocolSwapFee || '0') | ||
: pool.protocolVersion === 3 | ||
? parseFloat(pool.dynamicData.aggregateYieldFee || '0.1') |
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.
This also needs to changed in the networkconfig from 0.5 to 0.1 for v3. Also, why is it called aggregateYieldFee and not protocolYieldFee for v3 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.
AggregateYieldFee includes potential hook fees. We might not need a default since we always query for it on-chain. Do you agree?
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.
But aggregateYieldFee is still the same as protocolYieldFee?
think a default is save, I'd leave it
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’m not sure about aggregateYieldFee vs. protocolYieldFee. I assume protocolYieldFee can be added via the protocolFeeController, but most usage will likely remain with aggregateYieldFee.
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.
Lets create an issue for that to revisit and merge this
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.
added: #1225
No description provided.