MaticX Polygon Supply Cap Update
01Summary
This proposal increases the MaticX supply cap on Polygon v3 from 38M to 50.6M units (75% of current MaticX supply) to accommodate expected large deposits and enable yield-maximizing strategies during ongoing liquidity mining, while maintaining Aave DAO's maximum supported counterparty risk threshold.
- Type
- parameter change
Key changes
- MaticX Supply Cap increase from 38M to 50.6M units on Polygon v3(high)
- Supply cap utilization will decrease from 87.9% to approximately 70.6% after increase(medium)
- Enables accommodation of anticipated 10M-15M unit whale deposit from Stader Labs(high)
Notable concerns
- Large whale deposit (10M-15M units) from single entity may create concentration risk
- Supply cap set at maximum 75% threshold previously voted by Aave DAO, limiting future expansion without new governance vote
- Current supply cap utilization at 87.9% indicates rapid growth trajectory
Generated by Kvorum
02Description
Simple Summary
This publication proposes increasing the MaticX Supply Cap on Polygon v3 from 38.0M units to 50.6M units.
Motivation
The current Supply Cap’s utilisation is hovering around 87.9%, with 4.6M units of MaticX deposit capacity. Discussions with Stader Labs indicates a whale of approximately 10M-15M units is going to deposit on Aave v3. The current supply cap prohibites the full deposit and entering the yield maximising strategy.
With Liquidity Mining (LM) ongoing, MaticX deposit rewards (SD) and wMATIC borrowing rewards (stMATIC & MaticX), it is important that Aave DAO ensures there is adequate capacity to enable the yield maximising strategies to grow.
With an abundance of wMATIC deposits and LM ongoing, we are experiencing exception MaticX deposit growth.
To facilitate the continued growth of MaticX, this proposal seeks to increase the Supply Cap to 75% of supply on Polygon. This is the maximum counterparty risk Aave DAO has voted to support.
Current MaticX supply on Polygon is 67,440,058 units 1. Therefore the newly proposed Supply Cap is 50,600,000 units (rounded up).
With reference to the ARFC Aave V3 Caps update Framework and Direct to AIP Framework the preferred path forward is to implement several upgrades to gradually increase Aave’s MaticX exposure over time whilst bypassing Snapshot.
Specification
Ticker: MaticX
Contract: polygon: 0xfa68FB4628DFF1028CFEc22b4162FCcd0d45efb6 1
| Parameter | Current Value | Proposed Value |
|---|---|---|
| SupplyCap | 38M units | 50.6M units |
References
- Implementation: Polygon
- Tests: Polygon
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal describes a single, well-scoped parameter change: raising the MaticX supply cap on Aave v3 Polygon from 38.0M to 50.6M units. The decoded calldata shows only one top-level action: a generic execute(address) call on a mainnet contract, passing the address of a separate payload contract. This is the standard pattern for Aave's cross-chain governance (Direct-to-AIP framework referenced in the description itself), where the mainnet vote triggers execution of a payload contract whose internal logic (not decoded here) performs the actual PoolConfigurator.setSupplyCap() call on Polygon. Because the decoded action does not expose the specific numeric parameters being set on the Polygon pool, I cannot directly verify the 38M -> 50.6M change against calldata values. However, there is no evidence of any mismatch, extra action, or suspicious target — the single action is consistent with the described mechanism (execute a payload to update a cap), and the description explicitly explains this cross-chain execution path. Given the lack of granular calldata to confirm the exact cap values, confidence in a full numeric verification is low, but there is no indication of a discrepancy, so the overall assessment is consistent based on available information.
Generated by Kvorum
04Actions
- Target
- 0x158a…d45b
- Value
- 0 wei
- Function
- execute(address)
- Arguments
{ "0": "0x7afc6e6F5f009016DA501f40a2Ff96b3Fa7e2c09" }- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 320x329c…3ed4 | For | 247.6K | 41.53% | — | 3y ago |
| 070x0703…961b | For | 106.8K | 17.91% | — | 3y ago |
| 620x62a4…816a | For | 81.1K | 13.60% | — | 3y ago |
| B80xb83b…cf5c | For | 80K | 13.42% | — | 3y ago |
| B90xb933…8dd1 | For | 42K | 7.05% | — | 3y ago |
| E40xe459…e666 | For | 20K | 3.36% | — | 3y ago |
| EA0xea17…6676 | For | 15.3K | 2.56% | — | 3y ago |
| 180x1855…98ba | For | 3K | 0.50% | — | 3y ago |
| A00xa06c…61f7 | For | 283.3 | 0.05% | — | 3y ago |
| 050x0527…8469 | For | 24.9 | 0.00% | — | 3y ago |
| 680x680a…5d5f | For | 2.7 | 0.00% | — | 3y ago |
| 2F0x2f2f…f78a | For | 2 | 0.00% | — | 3y ago |
| 340x3486…e8de | For | 1.5 | 0.00% | — | 3y ago |
| 670x6799…ed9c | For | 1.4 | 0.00% | — | 3y ago |
| 290x2985…1b04 | For | 1.1 | 0.00% | — | 3y ago |
| 130x13ac…b2f4 | For | 1.1 | 0.00% | — | 3y ago |
| 700x70df…1889 | For | 1 | 0.00% | — | 3y ago |
| 300x3047…20e3 | For | 1 | 0.00% | — | 3y ago |
| 450x452b…9edb | For | 1 | 0.00% | — | 3y ago |
| 290x2963…c4bc | For | 1 | 0.00% | — | 3y ago |
| 5D0x5dee…de99 | For | 1 | 0.00% | — | 3y ago |
| 0A0x0ac4…3292 | For | 0.6 | 0.00% | — | 3y ago |
| 590x5990…4916 | For | 0.2 | 0.00% | — | 3y ago |
| 590x59d4…d115 | For | 0.2 | 0.00% | — | 3y ago |
| 500x50d2…5318 | For | 0.1 | 0.00% | — | 3y ago |
| 340x3496…126b | For | 0.1 | 0.00% | — | 3y ago |
| A10xa186…fc22 | For | 0.1 | 0.00% | — | 3y ago |
| EE0xeeda…e672 | For | 0.1 | 0.00% | — | 3y ago |
| EC0xec8e…39ef | For | 0 | 0.00% | — | 3y ago |
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aavedefeatedMaticX Polygon Supply Cap Update100%
- aaveexecutedMaticX Supply Cap Increase Polygon v396%
- aavecanceledMaticX Supply Cap Increase Polygon v394%
- aaveexecutedMaticX Supply Cap Increase Polygon v394%
- aaveexecutedMaticX Supply Cap Increase in Polygon V394%
- aaveexecutedPolygon Supply Cap Update92%
- aavedefeatedMaticX Supply Cap Increase Polygon v3 and AGD Approval92%
- aaveexecutedSupply Cap Update - stMATIC Polygon v391%
- aavecanceled[ARFC] Increase MaticX supply cap88%
- aaveexecuted[ARFC] Increase MaticX supply cap88%