KVORUM
aaveSource: Aave governor v2 · #95

Add LUSD to Aave V2

executedAug 28, 2022, 10:02 AM UTCbyF00xf060…45f8

01Summary

AISummary by Kvorumclaude-haiku-4-5

Add LUSD, an overcollateralized ETH-backed stablecoin from the immutable Liquity protocol, as a borrowable asset on Aave with 0% LTV to diversify away from centralized stablecoins.

Type
protocol addition

Key changes

  • Initialize LUSD reserve on Aave with 0% LTV (borrowing only, no collateral use)(high)
  • Enable variable borrowing for LUSD with configured interest rate strategy(high)
  • Connect LUSD price oracle (LusdUsdToLusdEth price feed) to AaveOracle(high)
  • Set reserve factor for LUSD(medium)

Notable concerns

  • LUSD borrowing only available at 0% LTV initially; LTV could be increased later if demand warrants
  • Dependency on Liquity protocol immutability; Liquity team mentioned working on synergetic project but details not provided
  • Current proposal does not enable stable borrowing or efficiency mode (v3)
  • Future changes dependent on mainnet v3 availability
Contracts0xe0070f7a961dcb102e3d904a170613be3f3b37a90x893E606358205AD294e610ad48e8aEF98aEadDbe0xEB1cfEF24F5B9d287F702AC6EbD301E606936B540x595c33538215DC4B092F35Afc85d904631263f4F0x545Ae1908B6F12e91E03B1DEC4F2e06D0570fE1b0x60c0b047133f696334a2b7f68af0b49d2F3D4F720x5f98805A4E8be255a32880FDeC7F6728C6568bA0
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

388 words

Simple Summary

Add LUSD as a borrowable asset on Aave (0% LTV), helping the protocol diversify its stablecoin offering away from centralized stablecoins.

Abstract

LUSD is stablecoin minted directly by the protocol users by opening a Trove and depositing ETH as collateral. Loans are interest-free, with a 0.5% base initiation fee. All the contracts of the Liquity protocol are immutable, which makes LUSD the most trustless stablecoin currently available on the Ethereum mainnet.

LUSD is overcollateralized by ETH with two main mechanisms helping it keep its peg: first, LUSD can be redeemed for ETH at face value (i.e., 1 LUSD for $1 of ETH). Secondly, there is a minimal collateral ratio of 110%. Both mechanisms respectively create a price floor and ceiling through arbitrage opportunities.

Since the protocol is immutable, no additional developments are planned, yet the Liquity team is working on another project that will prove synergetic with LUSD.

LUSD’s resilience makes it a highly sought-after stablecoin for DAOs and protocols looking to diversify their treasury and users looking for cost-effective leverage on ETH. The current focus is to grow the DeFi ecosystem around LUSD to enable more diverse use cases.

Motivation

Most of the stablecoins available for borrowing on Aave are centralized or relying heavily on centralized collateral, apart from FEI, sUSD and RAI. Adding LUSD as a borrowable asset on Aave would enable the protocol to further diversify away from centralized stablecoins.

Specification

This proposal initialises the LUSD reserve, enables variable borrowing and sets a reserve factor. As needed, it also connects a price source on the AaveOracle.

Rationale

LUSD will be added as a borrowable asset only (0% LTV) to ensure the safest onboarding possible. If the demand for borrowing is sufficient, the LTV could later be raised and once mainnet v3 is available, efficiency mode could also be enabled.

Test Cases

All the components involved in this proposal (tokens' implementations, interest rate strategy, oracle feed, proposal payload) have been tested and reviewed, including simulations on mainnet of the whole proposal lifecycle.

Link to Test Cases: End-to-end test suite

Implementation

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The proposal describes a single governance action: executing a pre-deployed payload contract (LUSDListingPayload) that initializes the LUSD reserve, sets it as borrowable with 0% LTV, configures a reserve factor, and connects an oracle price feed. The decoded calldata shows exactly one action: a call to execute() (via fallback) on the address 0xe0070f7a961dcb102e3d904a170613be3f3b37a9, which matches the LUSDListingPayload address explicitly linked in the Implementation section of the description. This is the standard Aave governance pattern where a single delegatecall to a payload contract performs all the detailed configuration steps described in prose (reserve init, LTV, borrowing enablement, reserve factor, oracle connection) — these details are not separately decoded here because they occur inside the payload's own logic via delegatecall, not as separate top-level calldata entries. Since the target address matches precisely what the description names, and there is no evidence of a different target, extra hidden calls, or conflicting values, the description and calldata align. Confidence is medium rather than high because the internal effects of the payload (the actual LTV value, reserve factor, oracle address) are not independently visible in the decoded action list — we can only verify that the correct payload contract is being executed, not that its internal logic exactly matches every numeric claim in the prose (e.g., 0% LTV, reserve factor). No numeric mismatches, target mismatches, or omissions are evident from what is decodable.

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
#0fallback()chain 0x1
Target
0xe007…37a9
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total
Filter:
VoterChoice% of totalRationale
C10xc17c…64e1For166.7K0.00%—4y ago
F00xf060…45f8For99.9K0.00%—4y ago
C40xc4a9…2935For92.5K0.00%—4y ago
550x55b1…f262For67.9K0.00%—4y ago
730x732a…b848For66.5K0.00%—4y ago
680x683a…6c02For62.7K0.00%—4y ago
1B0x1beb…d025For17.8K0.00%—4y ago
070x0703…961bFor10K0.00%—4y ago
390x39d8…d8adFor1.3K0.00%—4y ago
PIpizzallama.eth0x32a5…525dFor282.60.00%—4y ago
880x8899…0ebdFor94.20.00%—4y ago
390x39e9…cd36For78.90.00%—4y ago
A20xa2e4…b7d8For60.60.00%—4y ago
D30xd3b1…e1d2For51.70.00%—4y ago
AA0xaa7a…7d66For50.40.00%—4y ago
400x4053…4f15For42.70.00%—4y ago
C90xc960…5f0bFor22.40.00%—4y ago
740x742b…d2e0For19.90.00%—4y ago
B00xb012…831dFor16.40.00%—4y ago
9D0x9dbd…8a90For110.00%—4y ago
260x26ab…71e2For90.00%—4y ago
A00xa0ef…2d56For8.30.00%—4y ago
0B0x0b8a…765aFor8.10.00%—4y ago
100x10ec…0e3fFor3.40.00%—4y ago
1E0x1e51…9fa8For30.00%—4y ago
970x9730…14abFor2.40.00%—4y ago
070x0708…09acFor2.10.00%—4y ago
230x2385…9dc8For20.00%—4y ago
7B0x7b0b…abdeFor1.50.00%—4y ago
890x8960…3a8cFor1.50.00%—4y ago
DC0xdc52…7fa7For1.50.00%—4y ago
5E0x5e4d…cdc3For1.50.00%—4y ago
310x31ad…c703For1.50.00%—4y ago
6C0x6c3d…506dFor1.30.00%—4y ago
8F0x8f59…3d30For1.30.00%—4y ago
C10xc10f…ce24For1.30.00%—4y ago
A60xa60d…7b12For1.20.00%—4y ago
9E0x9e28…4886For1.20.00%—4y ago
B90xb9ed…08f6For1.20.00%—4y ago
830x8393…e15dFor1.20.00%—4y ago
EF0xefa8…039cFor1.20.00%—4y ago
CD0xcd79…cadfFor1.10.00%—4y ago
6C0x6c4a…acdbFor1.10.00%—4y ago
EC0xecd0…6d74For1.10.00%—4y ago
AD0xad7a…f871For1.10.00%—4y ago
780x7819…e609For1.10.00%—4y ago
1F0x1fe6…596bFor1.10.00%—4y ago
620x623a…5343For1.10.00%—4y ago
110x1115…a7dfFor1.10.00%—4y ago
950x9547…d2b0For1.10.00%—4y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.