KVORUM
aaveSource: Aave governor v2 · #56

Add Assets to Aave Polygon Market and Update WMATIC Risk Parameters

executedJan 27, 2022, 05:32 AM UTCbyC30xc3c2…9fe5

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal lists 6 tokens (BAL, CRV, DPI, LINK, SUSHI, GHST) on the Aave Polygon market with specified risk parameters, adds GHST as a new collateral asset to support the Aavegotchi ecosystem, and updates WMATIC risk parameters. This is Aave's first cross-chain governance proposal, executed via Ethereum mainnet vote with message bridged to Polygon.

Type
protocol addition

Key changes

  • List BAL, CRV, DPI, LINK, and SUSHI from AAVE V2 market on Aave Polygon Market with specified risk parameters (LTV 20-50%, Liquidation Threshold 45-65%, Reserve Factor 10-35%)(high)
  • Add GHST as new collateral asset on Polygon market with LTV 25%, Liquidation Threshold 45%, Liquidation Bonus 12.5%, Reserve Factor 20%(high)
  • Update WMATIC risk parameters: increase LTV from 50% to 65% and Liquidation Threshold from 65% to 70%(medium)
  • Enable borrowing on BAL, CRV, LINK, and GHST; disable borrowing on DPI and SUSHI(medium)
  • Set asset price sources on Aave Oracle for all newly listed assets(medium)

Notable concerns

  • Aave has existing investment relationship with Pixelcraft Studios (Aavegotchi developer) and Stani Kulechov serves as Aavegotchi advisor, presenting potential conflict of interest
  • GHST is relatively new token (15 months maturity) compared to established assets like LINK
  • GHST market cap of $140M and 24hr volume of $29.2M are considerably smaller than typical Aave collateral assets
  • Proposal requires functional cross-chain bridge infrastructure which is being used for the first time in Aave governance
Contracts0x26db2b833021583566323e3b8985999981b9f1f30x0229f777b0fab107f9591a41d5f02e4e98db6f2d0xdc9A35B16DB4e126cFeDC41322b3a36454B1F772
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

1,275 words

Simple Summary

This AIP would list BAL, CRV, DPI, GHST, LINK, and SUSHI from the AAVE V2 market on the Aave Polygon Market, and list GHST as a new asset to the Polygon market as collateral. WMATIC risk parameters are also being updated.

Rationale

BAL, CRV, DPI, LINK, and SUSHI have been voted in by governance to be added to the Polygon market. These tokens are already listed in the V2 market.

WMATIC parameters are being updated to maintain the overall risk tolerance of the protocol while making risk trade-offs between specific assets.

GHST is the token that powers the Aavegotchi universe. Aavegotchi (Playable DeFi-backed NFTs) utilizes Aave aTokens in game as collateral assets for Aavegotchis “playable bank”. Given Aave’s recent launch onto Polygon (where Aavegotchi is deployed) the Aavegotchi community believes it would be a great idea to have GHST token as collateral on Matic Aave. If GHST gets listed as an collateral on Aave, users of Aavegotchi will be able to use aGHST as collateral within their Aavegotchis.

Motivation

With the availability of cross chain governance, it's time to make long overdue updates to the Polygon market.

Specifications

The risk parameters for the assets coming from the V2 market to the Polygon market are as follows:

BAL

  • LTV: 20%
  • Liquidation Threshold: 45%
  • Liquidation Bonus: 10%
  • Reserve Factor: 20%

CRV

  • LTV: 20%
  • Liquidation Threshold: 45%
  • Liquidation Bonus: 10%
  • Reserve Factor: 20%

DPI

  • LTV: 20%
  • Liquidation Threshold: 45%
  • Liquidation Bonus: 10%
  • Reserve Factor: 20%
  • Not borrowable

LINK

  • LTV: 50%
  • Liquidation Threshold: 65
  • Liquidation Bonus: 7.5%
  • Reserve Factor: 10%

SUSHI

  • LTV: 20%
  • Liquidation Threshold: 45%
  • Liquidation Bonus: 10%
  • Reserve Factor: 35%
  • Not borrowable

Adding GHST to the Polygon Market

  1. Aavegotchis are crypto-collectibles (NFT). Aavegotchis are pixelated ghosts living on the Matic blockchain, backed by the ERC-721 standard. Their value is determined by rarity level 2, which is calculated via multiple factors, such as base traits, amount of staked collateral 2, and equipped wearables. GHST token is the backbone of Aavegotchi Realm. GHST is an in-game asset, used in all operations in-game (excluding usage of GHST as a collateral for summoning your Aavegotchi, which are aTokens powered by Aave) such as buying portals (opened\closed), wearable items, potions and etc.

  2. Users of Aavegotchi will borrow GHST, to use it as an in-game asset, to speculate on in-game values or for other in-game purposes. Users of Aavegotchi will use it as a collateral to summon their gotchis with it because aTokens are another backbone of the game. To summon your Aavegotchi you need to have a specific amount of aTokens to make it possible.

  3. GHST token has been live on Ethereum Mainnet since September, when it was launched via a continuous bonding curve DAICO sale (still live today at aavegotchi.com/curve 5). The token was launched at 0.2 DAI / GHST and currently sits at around 1.2 DAI. The all-time high is around 1.9 DAI / GHST. GHST is priced in DAI because unlike most tokens in crypto, it is actually backed by a DAI reserve at a 33% connecting weight. This makes the price more stable because it takes more in/out to change the price.

A significant challenge for Aavegotchi as a project was deciding to migrate our ecosystem from Ethereum to Polygon (then known as Matic). Expensive gas fees would have made it impossible for our players to use Aavegotchi NFTs (which require constant onchain attention). However, from January to March, we were able to complete the migration and launch successfully onto Polygon.

  1. GHST is the official utility token of the Aavegotchi ecosystem and can be used to purchase portals, wearables, and consumables.

  2. The inflation of GHST tokens through purchases on the bonding curve is positively correlated to the GHST price. The bonding curve has been mathematically programmed to increase the price of GHST as the circulating supply of GHST increases.

  3. The bonding curve has minting and burning permissions, but these permissions are governed by the AavegotchiDAO which exists on Ethereum Mainnet. GHST tokens are not arbitrarily minted or burned. The supply is determined by inputs via the bonding curve.

Market Data

  • Market Cap - $140,000,000
  • 24hr Trading volume - $29,209,070
  • Currently listed on 14 exchanges: Binance, Okex, Poloniex, Uniswap, Gate.io, LBank, Bilaxy, Hoo, MXC, BiBox, 0x, BamBoo Relay, QuickSwap, 1ich Exchange;
  • Maturity - 15 months.

Proposed Risk Parameters

  • LTV: 25%
  • Liquidation Threshold: 45%
  • Liquidation Bonus: 12.5%
  • Reserve Factor: 20%

Socials

Token Stats

  • Contract’s date of deployments: 14 September 2020 (Ethereum)
  • Number of transactions:
    • Ethereum: 143,397
    • Polygon: 2,507,992
  • Number of holders for tokens:
    • Ethereum: 6,427
    • Polygon: 68,943
  • Currently circulating Supply - 66,419,514
  • Current total supply - 66,419,514

Full Disclosure

Stani Kulechov is an official advisor of Aavegotchi, and Aave has invested into Pixelcraft Studios, the development team behind Aavegotchi.

WMATIC Risk Parameter Update

The criteria for assessing market risk, as determined by the market size and changes in fluctuation in demand, is presented by the Aave community here. In line with the criteria, analysis of the MATIC token on Polygon network is presented below:

Holders:168,102B+ to A-B+
Transactions100,240,631A
Mkt Cap586,568,252B+ to A-
Av. Vol.$50,675,854C+ to B-
Norm. Vol0.06579C+ to B-

The MATIC token risk score compiled by Index Coop is B+. This matches the risk score cited here 1. However, the volatility score of B- (C+ to B-) is justified by the 0.06579 score compared to 0.064 in the table presented in the documentation 1. Further to this, assets like BAL and BAT on Ethereum have similar vol characteristics to wMATIC on Polygon. The Norm. Vol parameter is the average of the t=30 days and t=90 days as shown in the below table.

wMATIC Volatility Data (Polygon Network Data)

TimeS.D Vol
t=7 days0.08475
t=30 days0.06535
t= 90 days0.06622
t= 180 days0.09013
t= 365 daysNA

Based upon the volatility data share above, Index Coop suggests changing the Liquidation Threshold and Loan to Value parameters as shown below:

ParameterCurrent ValueRecommended Value
wMATIC Liquidation Threshold65%70%
wMATIC Loan to Value50%65%

Implementation

This proposal is the first cross chain proposal for AAVE. AAVE holders will vote through the Ethereum mainnet to change parameters on the Polygon market. The proposal makes use of the cross chain bridge to send a message to the Polygon bridge executor. The following functions are called on the lending pool configurator from the executor:

For GHST, BAL, DPI, CRV, SUSHI, LINK:

  • batchInitReserve((address aTokenImpl, address stableDebtImpl, address variableDebtImpl, uint8 decimals, address interestRateStrategy, address underlyingAsset, address treasury, address incentivesController, string underlyingAssetName, string aTokenName, string aTokenSymbol, string varTokenName, string varTokenSymbol, string stableDebtName, string stableDebtSymbol, bytes params)[])
  • setReserveFactor(address asset, uint256 reserveFactor)

For GHST, BAL, CRV, LINK:

  • enableBorrowingOnReserve(address asset, bool stableBorrowEnabled)

For GHST, BAL, DPI, CRV, SUSHI, LINK, WMATIC:

  • configureReserveAsCollateral(address asset, uint256 ltv, uint256 liquidationThreshold, uint256 liquidationBonus)

And the following function is called on the Aave Oracle for GHST, BAL, DPI, CRV, SUSHI, LINK:

  • setAssetSources(address[] assets, address[] sources)

A payload contract has been created to initiate all the above changes.

Payload Contract

Tests and implementation are located here.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The proposal is a cross-chain governance action. The only decoded on-chain action is a single call to sendMessageToChild on the Ethereum-side bridge (Fx-Portal state sender), targeting the Polygon bridge executor address 0xdc9A35B16DB4e126cFeDC41322b3a36454B1F772 — exactly the address cited in the description's Implementation section. The embedded bytes payload, when decoded, references an 'execute()' call directed at 0x8b97a0b37974ddec0cb8b8039a4e593457defe8c, which is precisely the Payload Contract address linked in the description. This confirms the top-level action matches the description's stated mechanism (cross-chain message → bridge executor → payload contract execute()) with correct addresses on both ends. However, the granular risk-parameter changes described in the prose (specific LTV, Liquidation Threshold, Liquidation Bonus, Reserve Factor values for BAL, CRV, DPI, GHST, LINK, SUSHI, and the WMATIC LTV/LT update) are not independently verifiable from this single decoded action, since those parameters are encoded inside the payload contract's own bytecode/logic rather than appearing as separate decoded calldata arguments here. Because the visible action matches the description's own account of how the proposal works (same target addresses, same execute() pattern), I found no target, value, or omission discrepancies at the level that can be checked. Confidence is medium rather than high because the specific numeric risk parameters claimed in the prose could not be cross-verified against decoded data beyond the message-passing wrapper.

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
#0sendMessageToChild(address,bytes)chain 0x1
Target
0xfe5e…89a2
Value
0 wei
Function
sendMessageToChild(address,bytes)
Arguments
{
  "0": "0xdc9A35B16DB4e126cFeDC41322b3a36454B1F772",
  "1": "0x00000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000010000000000000000000000008b97a0b37974ddec0cb8b8039a4e593457defe8c00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000009657865637574652829000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001"
}
Calldata

05Tally

Summed from votes

Voters94
VP participating369.4K
Outcome (current)For
Current support100%

06Voters

94 total
Filter:
VoterChoice% of totalRationale
DD0xdd70…8202For134.1K36.31%—5y ago
C30xc3c2…9fe5For97.9K26.51%—5y ago
9B0x9b5e…0499For78K21.10%—5y ago
BA0xbad1…b25dFor38K10.29%—5y ago
1B0x1beb…d025For17.1K4.64%—5y ago
7B0x7bf1…163bFor2K0.54%—5y ago
F50xf569…271bFor1.2K0.32%—5y ago
AC0xac39…fdd0For2000.05%—5y ago
B40xb484…a1c3For1550.04%—5y ago
470x47d6…b853For132.90.04%—5y ago
0X0x808.eth0x808a…e43eFor100.10.03%—5y ago
E90xe913…c6e5For85.70.02%—5y ago
2C0x2c12…386dFor76.20.02%—5y ago
080x0871…ba80For40.40.01%—5y ago
950x956f…3f92For310.01%—5y ago
620x62a4…816aFor30.70.01%—5y ago
2B0x2ba0…9a9dFor21.10.01%—5y ago
6B0x6bac…342cFor210.01%—5y ago
240x2477…b7a8For200.01%—5y ago
7B0x7bb7…e435For19.80.01%—5y ago
AA0xaabd…e883For13.90.00%—5y ago
D70xd7ef…c722For11.10.00%—5y ago
400x40cf…371cFor9.90.00%—5y ago
3B0x3bbf…e60fFor9.40.00%—5y ago
DA0xda5b…31c9For7.90.00%—5y ago
CE0xce93…e5a2For7.10.00%—5y ago
F50xf5fe…f6fbFor6.90.00%—5y ago
8C0x8cf7…94edFor6.70.00%—5y ago
E20xe295…f268For5.80.00%—5y ago
000x002d…6884For5.50.00%—5y ago
590x59bd…050aFor5.40.00%—5y ago
120x12ef…9c17For5.30.00%—5y ago
E00xe0c4…eebfFor4.80.00%—5y ago
E20xe23d…8defFor3.90.00%—5y ago
410x41ad…bf46For3.30.00%—5y ago
C00xc0af…574fFor3.20.00%—5y ago
630x6372…adf4For3.20.00%—5y ago
F20xf2b9…9e63For2.90.00%—5y ago
C50xc54a…4592For2.70.00%—5y ago
6B0x6bdf…df63For2.60.00%—5y ago
490x49e3…a4baFor2.50.00%—5y ago
BB0xbb46…72a7For2.30.00%—5y ago
490x4984…5ef4For20.00%—5y ago
2D0x2d5f…66efFor20.00%—5y ago
DF0xdf14…c92aFor20.00%—5y ago
690x69a2…938fFor1.80.00%—5y ago
E20xe2ed…d09bFor1.70.00%—5y ago
A50xa532…1035For1.60.00%—5y ago
5B0x5b0f…38eaFor1.50.00%—5y ago
9B0x9b8c…1699For1.30.00%—5y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.