[Agill-Sheron]

Not for merging as is. This is a hand-off for Aave's engineering team to take over: the options run on simulated data and sit behind a review-only Tweaks popover. Pick a direction, lock it in, and wire the real contract reads before it ships.

Design-review options for reserves with a dynamic borrow cap (current cap kept just above total borrowed, raised automatically up to a max cap). Against the current cap alone, these reserves look nearly full all the time; these options show the max cap instead.

General Changes

• Reserve page (?dyncap=): Today (default, unchanged) · Notice · Max cap · Vs max · Combined. Vs max and Combined add a usage bar on the max cap scale, with optional hover tooltips (?barhover=).
• Markets page: notice, tag and a Dynamic cap column, each toggled on its own (?mktnotice=, ?mkttag=, ?mktcol=).
• Borrow modal and reserve actions: notes for available now, cap used up, and max cap reached.
• Dashboard borrow list: compact dynamic cap hint.

Developer Notes

• Every option sits behind a floating Tweaks popover, active only in next dev or with NEXT_PUBLIC_ENABLE_TWEAKS=true. Production always shows Today.
• Data is simulated until the contracts ship: simulatedCaps.ts marks Arbitrum v3 USDC as dynamic (?capstate= picks the state), and simulatedWallet.ts (?wallet=small|large) fakes a read-only position so the borrow flow can be reviewed without a wallet. The header of simulatedCaps.ts lists the contract reads that replace it.
• DYNAMIC_CAPS_LEARN_MORE_URL is a placeholder.

Once an option is chosen

Lock it in and remove the review scaffolding. Example prompt for a coding agent:

Lock in the dynamic borrow cap options: reserve page Combined, bar hover on, markets page notice on, tag off, column off. Hardcode these as the only behaviour, delete the other options and their branches, and remove the Tweaks popover (DynamicCapsTweaks, src/components/tweaks/*, the useTweakParam calls and URL params, and its mount in _app.page.tsx). Keep the simulated data until the contracts are deployed, then replace it with the real reads described in simulatedCaps.ts.

---

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 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)

[vercel]

@Agill-Sheron is attempting to deploy a commit to the Aave Team on Vercel.

A member of the Team first needs to authorize it.