feat: implement underlying token APYs

[MartinGbz]

General Changes

• Adds underlying tokens APY to:

  • Dashboard page in "Supply" & "Borrow" sections
  • Markets page

• Desktop & Mobile are managed

• Only the sum of both APYs is displayed, a tooltip button has been added to see the APY details (Supply/Borrow APY & Underlying APY)

• APY are fetched/compute using onchain data. But if the onchain fetch failed (eg: no events during the last week), there is for each token a backup function that use an API (except for the cbETH that returns 0 because I didn't found any official API, so no underlying APY will be display in this case).

  Q: what are the chances (no events during the last week) ?
  A:

  • sDAI => null, cause we do a contract call
  • stETH, ETHx, weETH, cbETH, rETH => almoast 0, based on the event history, there is always 1 "rebase" event per day (except for weeETH that has 4 event per day), and it's been going on for a long time. If you want I can provide you the list of Rebase event of eacj LST so you can check by yourself.

  But event if one day is 1 day without event, I take the last and latest event from a period of 1 week, so the front will use backup function only if there are no events during the last 7 days. But if you want we can increase it for 14 days to be full safe, I'm just afraid about RPC range block error / rate limit.

APYs Implemented:

• wstETH
• weETH
• sDAI
• rETH
• ETHx
• cbETH

Developer Notes

I didn't implement the APY in the migration page because I think it's clearer to keep only Aave Supply APYs here.

For the fork mode, I set the max block range (for event logs fetching) to 1k. Because on some cases, tenderly provide RPC with only 1k max block range capacity per request. This make the fetch slower, but because it's only on fork env it's alright. For the prod mode we use 100k block as max range.

General Notes:

• I noticed that the SupplyAssetsListMobileItem.tsx file wasn't used because there's already a SupplyAssetsListItemMobile component in the SupplyAssetsListItem.tsx file.
  I proposed to either remove the SupplyAssetsListMobileItem.tsx file or remove the SupplyAssetsListItemMobile include in the SupplyAssetsListItem.tsx file and use the one in SupplyAssetsListMobileItem.tsx

Let me know :))

---

Author Checklist

Please ensure you, the author, have gone through this checklist to ensure there is an efficient workflow for the reviewers.

• The base branch is set to main
• The title is using Conventional Commit formatting
• The Github issue has been linked to the PR in the Development section
• The General Changes section has been filled out
• Developer Notes have been added (optional)

If the PR is ready for review:

• The PR is in Open state and not in Draft mode
• The Ready for Dev Review label has been added

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.

• End-to-end tests are passing without any errors
• Code style generally follows existing patterns
• Code changes do not significantly increase the application bundle size
• If there are new 3rd-party packages, they do not introduce potential security threats
• If there are new environment variables being added, they have been added to the .env.example file as well as the pertinant .github/actions/* files
• There are no CI changes, or they have been approved by the DevOps and Engineering team(s)
• Code changes have been quality checked in the ephemeral URL
• QA verification has been completed
• There are two or more approvals from the core team
• Squash and merge has been checked

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[foodaka]

all contract addresses should be pulled from the aave-address-book. If they are not they should be added https://github.com/bgd-labs/aave-address-book

[MartinGbz]

I've just push a PR on the address book repo
I'll tag you once the modifications will be done on this PR

[sakulstra]

Chiming in here as a maintainer of address-book.

We don't really want to list these addresses on address-book. The reason is that address book first and foremost is a library for usage in solidity and these addresses (for now) have no value for solidity devs

This repository contains an up-to-date registry of all addresses of the Aave ecosystem's smart contracts, for its usage in Solidity codebases.

The js export is a low effort feature we added at a later point to also expose these addresses in js(why not expose them when we already have them). This by no means implies though, that we'll add any address that might be useful in js on the address-book as this always comes at a cost for the solidity users of the library.

---

This out of the way, i had a quick look at what is done here and want to share my 2ct:

1. I think what @MartinGbz did here is quite valuable and could be useful for other ecosystem projects. I'd like to encourage you to develop this as an independent & modular package so you can rely on viem, multicall etc. We'd be happy to help & contribute.
2. probably it would be better to use getLogs with a topics filter over queryFilter. The reason is that queryFilter is not as widely supported and buggy on some node implementations.
3. For use in an ui (like this one) I think it's quite wasteful to actually do what is done here. Every user will need to do multiple api calls, fetch events over time and do calculations etc. Offloading unnecessary work to the client comes as a big cost and might cause rate-limits being reached on the 3th party endpoints. I would highly encourage the maintainers of this app to put 1) behind some cached api so users have to do a single request and not calculate anything clientside.

[github-actions]

❌ CI run has failed!
Please see logs at https://github.com/aave/interface/actions/runs/9762347615'

[github-actions]

📦 Next.js Bundle Analysis for aave-ui

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	539.29 KB (🟡 +1.5 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Nine Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/	76.97 KB (🟢 -127 B)	616.26 KB
/faucet	28.32 KB (🟡 +1 B)	567.61 KB
/governance	88.11 KB (🟢 -487 B)	627.4 KB
/governance/v3/proposal	128.38 KB (🟢 -479 B)	667.67 KB
/history	36.5 KB (🟢 -422 B)	575.79 KB
/markets	30.93 KB (🟢 -228 B)	570.22 KB
/reserve-overview	24.19 KB (🟢 -8 B)	563.48 KB
/staking	25.75 KB (🟢 -828 B)	565.04 KB
/v3-migration	41.7 KB (🟢 -485 B)	580.99 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[github-actions]

❌ CI run has failed!
Please see logs at https://github.com/aave/interface/actions/runs/10218562042'

[github-actions]

📦 Next.js Bundle Analysis for aave-ui

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	552.44 KB (🟡 +7.71 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Ten Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/	73.59 KB (🟢 -212 B)	626.03 KB
/bridge	44.04 KB (🟢 -553 B)	596.48 KB
/faucet	23.75 KB (🟡 +2 B)	576.18 KB
/governance	83.37 KB (🟢 -836 B)	635.81 KB
/governance/v3/proposal	123.65 KB (🟢 -522 B)	676.09 KB
/history	31.94 KB (🟢 -426 B)	584.37 KB
/markets	27.03 KB (🟢 -387 B)	579.47 KB
/reserve-overview	19.79 KB (🟡 +4 B)	572.23 KB
/staking	21.17 KB (🟢 -833 B)	573.61 KB
/v3-migration	37.5 KB (🟢 -536 B)	589.94 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.