KVORUM
aaveSource: Aave governor v2 · #278

MaticX Polygon Supply Cap Update

executedJul 29, 2023, 07:37 AM UTCby320x329c…3ed4

01Summary

AISummary by Kvorumclaude-haiku-4-5

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
Contracts0xfa68FB4628DFF1028CFEc22b4162FCcd0d45efb6
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

261 words

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

ParameterCurrent ValueProposed Value
SupplyCap38M units50.6M units

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

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
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0execute(address)chain 0x1
Target
0x158a…d45b
Value
0 wei
Function
execute(address)
Arguments
{
  "0": "0x7afc6e6F5f009016DA501f40a2Ff96b3Fa7e2c09"
}
Calldata

05Tally

Summed from votes

Voters29
VP participating596.1K
Outcome (current)For
Current support100%

06Voters

29 total
Filter:
VoterChoice% of totalRationale
320x329c…3ed4For247.6K41.53%—3y ago
070x0703…961bFor106.8K17.91%—3y ago
620x62a4…816aFor81.1K13.60%—3y ago
B80xb83b…cf5cFor80K13.42%—3y ago
B90xb933…8dd1For42K7.05%—3y ago
E40xe459…e666For20K3.36%—3y ago
EA0xea17…6676For15.3K2.56%—3y ago
180x1855…98baFor3K0.50%—3y ago
A00xa06c…61f7For283.30.05%—3y ago
050x0527…8469For24.90.00%—3y ago
680x680a…5d5fFor2.70.00%—3y ago
2F0x2f2f…f78aFor20.00%—3y ago
340x3486…e8deFor1.50.00%—3y ago
670x6799…ed9cFor1.40.00%—3y ago
290x2985…1b04For1.10.00%—3y ago
130x13ac…b2f4For1.10.00%—3y ago
700x70df…1889For10.00%—3y ago
300x3047…20e3For10.00%—3y ago
450x452b…9edbFor10.00%—3y ago
290x2963…c4bcFor10.00%—3y ago
5D0x5dee…de99For10.00%—3y ago
0A0x0ac4…3292For0.60.00%—3y ago
590x5990…4916For0.20.00%—3y ago
590x59d4…d115For0.20.00%—3y ago
500x50d2…5318For0.10.00%—3y ago
340x3496…126bFor0.10.00%—3y ago
A10xa186…fc22For0.10.00%—3y ago
EE0xeeda…e672For0.10.00%—3y ago
EC0xec8e…39efFor00.00%—3y ago
Showing 29

07Forum

No forum thread is confidently linked to this proposal.