fix: cooldown period updated #2725
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
💡 Enable Vercel Agent with $100 free credit for automated AI reviews |
| const { data: stakeGeneralResult } = useGeneralStakeUiData(currentMarketData, stakeAssetName); | ||
|
|
||
| const stakeData = stakeGeneralResult?.[0]; | ||
| const stakeCooldownSeconds = stakeData?.stakeCooldownSeconds || 0; |
There was a problem hiding this comment.
we were just showing default right?
There was a problem hiding this comment.
We were displaying a hardcoded value equal to 20 days. I updated to show the cooldown value coming from the SC, and giving a hardcoded fallback equal to 7 days
There was a problem hiding this comment.
Actually, I’m thinking that the proposal only changed the cooldown period for AAVE, so I need to adjust the fallback to make sure it doesn’t affect other scenarios.
There was a problem hiding this comment.
can we read from the contract directly?
|
📦 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! 🙌 |
|
📦 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! 🙌 |
3 participants
General Changes
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