-
Notifications
You must be signed in to change notification settings - Fork 463
feat: added support for multiple rewardedassets per campaign #2756
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 latest updates on your projects. Learn more about Vercel for GitHub.
|
|
📦 Next.js Bundle Analysis for aave-uiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
| > | ||
| <Box sx={{ display: 'inline-flex', alignItems: 'center' }}> | ||
| <FormattedNumber | ||
| value={merklIncentives.breakdown.isBorrow ? -reward.apr : reward.apr} |
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.
should we convert apr to apy
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.
Bad variable names from me, I’ve changed them now for clarity.
| ? -merklIncentives.breakdown.merklIncentivesAPR | ||
| : merklIncentives.breakdown.merklIncentivesAPR |
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.
apr to apy?
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.
|
📦 Next.js Bundle Analysis for aave-uiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |

General Changes
Refactored the incentives Merkl code to support multiple rewarded assets within a single campaign, as well as multiple campaigns targeting the same aToken/vToken with different rewarded tokens.
Based the filtering on the onChainCampaignId, which is unique for each rewarded token, simplifying the code and making it agnostic to these different scenarios.
Developer Notes
Reviewer Checklist
Please ensure you, as the reviewer(s), have gone through this checklist to ensure that the code changes are ready to ship safely and to help mitigate any downstream issues that may occur.
.env.examplefile as well as the pertinant.github/actions/*files