Skip to content
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

Merged
merged 2 commits into from
Dec 4, 2024
Merged

new aave aprs and default yield fee #1224

merged 2 commits into from
Dec 4, 2024

Conversation

gmbronco
Copy link
Collaborator

@gmbronco gmbronco commented Dec 4, 2024

No description provided.

Copy link

changeset-bot bot commented Dec 4, 2024

🦋 Changeset detected

Latest commit: 8d42488

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
backend Minor

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')
Copy link
Collaborator

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?

Copy link
Collaborator Author

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?

Copy link
Collaborator

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

Copy link
Collaborator Author

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.

Copy link
Collaborator

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added: #1225

@gmbronco gmbronco merged commit 751e1e8 into v3-canary Dec 4, 2024
1 check passed
@gmbronco gmbronco deleted the new-aprs branch December 4, 2024 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants