KVORUM
aaveSource: Aave governance v3 · #32

MaticX Supply Cap Increase in Polygon V3

executedFeb 26, 2024, 03:32 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Increase the MaticX supply cap on Polygon V3 from 62M to 75M to accommodate growing user demand for deposits and enable recursive yield strategies. MaticX deposits have consistently exceeded 95% of the current supply cap, and this increase aligns with prior DAO decisions to maintain aggressive supply caps for correlated assets.

Type
parameter change

Key changes

  • Increase MaticX Supply Cap on Polygon V3 from 62M to 75M(high)
ContractsAaveV3Polygon
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

219 words

Simple Summary

This proposal aims to increase the MaticX Supply Cap on Polygon V3 to match market demand.

Motivation

Increasing the supply cap of Polygon MaticX in the Aave market is a strategic move to accommodate growing demand, and follow a previous DAO decision to maintain aggressive supply caps for correlated assets.

Deposits of MaticX have been over 95% of the supply cap for some time. Increasing the Supply Cap will enable users to continue depositing MaticX and enter the recursive MaticX/wMATIC yield strategy.

The DAO has previously voted to allow assets with correlated borrow supply caps to be up to 75% of cumulative supply. Since this exceeds the supply cap increase allowable by risk stewards, this proposal will increase supply caps through the typical ARFC process. Current circulating supply is over 100M, so this proposal will increase the supply cap to 75M.

Specification

Increase the supply cap for MaticX on Polygon V3 to the following.

ParameterCurrent ValueProposed Value
SupplyCap62M75M

Useful Links

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

0 total

This proposal carries no on-chain actions.

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.