Renew LlamaRisk as Risk Service Provider - Epoch 4
01Summary
Aave DAO renews LlamaRisk as Risk Service Provider for one year to maintain critical risk infrastructure across Aave V3, V4, and Horizon. LlamaRisk will receive 1.5M GHO upfront, 1.5M GHO streamed over one year, and 5,000 AAVE streamed over one year. The engagement expands to cover protocol-owned risk infrastructure on Chainlink CRE, dynamic parameter automation, safety mechanisms, governance review, and R&D for V4-native systems.
- Type
- treasury allocation
- Funding
- $3,000,000 GHO + 5,000 AAVE
Key changes
- Cancel existing GHO stream (ID 100071) and transfer 1.5M aEthLidoGHO to LlamaRisk multisig(high)
- Create new 1.5M GHO stream over 365 days to LlamaRisk(high)
- Create new 5,000 AAVE stream over 365 days to LlamaRisk(medium)
- Expand LlamaRisk's scope to cover Aave V3, V4, Horizon, and protocol-owned risk infrastructure(high)
- Establish protocol-owned risk infrastructure on Chainlink CRE to reduce DAO dependence on closed systems(high)
Notable concerns
- LlamaRisk dependency risk for critical infrastructure; proposal aims to mitigate by building DAO-controlled infrastructure
- LlamaRisk phasing out non-Aave work over six months, scaling team to 20+ contributors during engagement
Generated by Kvorum
02Description
Simple Summary
This AIP renews LlamaRisk as a Risk Service Provider for Aave for one year.
Aave’s risk layer recently lost critical infrastructure operated by a departing risk provider, including automated risk-oracle infrastructure, parameter automation pipelines, and Risk Steward coverage. LlamaRisk stepped in with Aave Labs to assume control of the Risk Steward and maintain operational continuity across Aave markets.
The immediate issue is continuity.
The structural issue is ensuring Aave does not depend on risk infrastructure the DAO cannot inspect, verify, or replace without disruption.
This renewal expands LlamaRisk’s scope across Aave V3, Aave V4, and Horizon, with a focus on protocol-owned risk infrastructure built on Chainlink CRE. This moves Aave’s risk layer toward infrastructure owned and controlled by the DAO, with off-chain logic independently verifiable through cryptographic workflow IDs.
LlamaRisk will deliver:
- Protocol-owned risk infrastructure on Chainlink CRE.
- Risk-managed price feeds for Pendle PTs, CAPO assets, USDe, RWA NAV, and related integrations.
- Dynamic parameter automation for supply caps, borrow caps, interest rates, Umbrella calibration, credit lines, risk premiums, and liquidation configuration.
- Safety mechanisms including freeze guardians and V4 per-Spoke circuit breakers.
- Risk Steward co-ownership and operational accountability.
- AIP and governance payload review.
- Guardian signer duties.
- Monitoring, dashboards, escalation playbooks, and incident response support.
- Continued Horizon cooperation and LlamaGuard NAV expansion.
- R&D for V4-native risk systems, including RWA liquidation infrastructure and instant settlement infrastructure.
- Legal and regulatory research covering stablecoins, custody, counterparty risk, DeFi lending compliance, and tokenized RWA structuring.
LlamaRisk is currently a team of 16 contributors and expects to scale to 20+ contributors during this engagement. LlamaRisk also proposes to phase out remaining non-Aave work over six months and become Aave-exclusive by the midpoint of the engagement.
The approved compensation structure is:
| Component | Amount | Payment Method |
|---|---|---|
| Upfront payment | 1,500,000 GHO | Immediate payment |
| Streamed payment | 1,500,000 GHO | Linear stream over one year |
| Streamed payment | 5,000 AAVE | Linear stream over one year |
The current GHO stream with ID 100071 will be terminated.
Motivation
This proposal renews LlamaRisk as a Risk Service Provider for Aave following DAO discussion and Snapshot approval.
LlamaRisk’s role has expanded beyond its original mandate and now covers risk work across Aave V3, Aave V4, Horizon, governance review, market monitoring, Guardian signer duties, and protocol-owned risk infrastructure.
The renewal also addresses a near-term continuity need. With a departing risk provider no longer covering critical risk infrastructure and operational processes, the DAO needs to maintain coverage across active markets while reducing reliance on closed systems that are difficult for the DAO to inspect, verify, or replace.
Under this engagement, LlamaRisk will continue supporting Aave risk operations and contribute to protocol-owned risk infrastructure, including Chainlink CRE-based risk oracles, dynamic parameter tooling, LlamaGuard expansion, V4-native risk systems, and Horizon-related risk work.
The full scope, rationale, and budget were discussed through the ARFC process and approved by Snapshot. This AIP implements the approved renewal terms.
Specification
The payload performs the following actions on Ethereum mainnet:
- Cancel the existing GHO stream (ID
100071) onAaveV3EthereumLido.COLLECTOR. - Transfer
1,500,000 aEthLidoGHOfromAaveV3EthereumLido.COLLECTORto the LlamaRisk-controlled multisig at0x9eE16dBDE572886342fc1e2Db8525DEFB007b27c. - Create a new
aEthLidoGHOstream of1,500,000over365 daysto the same recipient, viaCollectorUtils.stream()onAaveV3EthereumLido.COLLECTOR. - Create a new
AAVEstream of5,000over365 daysto the same recipient, viaAAVE_ECOSYSTEM_RESERVE_CONTROLLER.createStream()onMiscEthereum.ECOSYSTEM_RESERVE. The stream amount is rounded down to the nearest multiple of the duration to avoid revert in the underlying controller.
References
- Implementation: AaveV3EthereumLido
- Tests: AaveV3EthereumLido
- Snapshot: https://snapshot.box/#/s:aavedao.eth/proposal/0x139144f55e87579003f5f9ed53fc4b87bd0c7312fc9c356e5e4e164baa3f8077
- Discussion
Disclaimer
LlamaRisk receives compensation from the Aave DAO for serving as a Risk Service Provider, as specified in this proposal.
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The decoded calldata contains only one action: a generic execute()/fallback() call to a payload contract address, with no further decoded arguments. This is the typical Aave governance pattern in which the on-chain proposal simply triggers a delegatecall to a dedicated Solidity payload contract (linked in the References section) that internally performs the specific steps described in the Specification (cancelling stream 100071, transferring 1.5M aEthLidoGHO, creating new GHO and AAVE streams). Because the decoded action set does not expose these internal steps, arguments, or recipient addresses, I cannot directly verify the specific amounts, stream IDs, or recipient address quoted in the description against the calldata provided. Nothing in the single decoded action contradicts the description, and the pattern itself (single execute() call routing to a payload contract) is standard and expected for Aave AIPs, so I do not flag this as a discrepancy. However, since verification of the granular financial details (1.5M GHO upfront, 1.5M GHO stream, 5,000 AAVE stream, recipient multisig address, stream cancellation ID) is not possible from the calldata alone, confidence in this comparison is low rather than high or medium.
Generated by Kvorum
04Actions
- Target
- 0x5f21…6ddb
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 330x3320…3bb7 | For | 107.2K | 27.69% | — | 6mo ago |
| 2C0x2cc1…4df1 | For | 88.6K | 22.88% | — | 6mo ago |
| 8B0x8b37…2a22 | For | 75.8K | 19.56% | — | 6mo ago |
| B90xb933…8dd1 | For | 53.9K | 13.93% | — | 6mo ago |
| EC0xecc2…6ac9 | For | 29.5K | 7.62% | — | 6mo ago |
| DF0xdf71…a51f | For | 11.7K | 3.02% | — | 6mo ago |
| 070x0703…961b | For | 10K | 2.58% | — | 6mo ago |
| 7A0x7ae1…e585 | For | 10K | 2.58% | — | 6mo ago |
| 3D0x3ddc…05b0 | For | 369.1 | 0.10% | — | 6mo ago |
| 7F0x7fd5…caaf | For | 115.5 | 0.03% | — | 6mo ago |
| 1B0x1b26…9bda | For | 40.6 | 0.01% | — | 6mo ago |
| BC0xbcf0…46a5 | Against | 6 | 0.00% | — | 5mo ago |
| 050x05f7…946c | For | 0.2 | 0.00% | — | 6mo ago |
| 530x53da…c14b | For | 0 | 0.00% | — | 6mo ago |
| CB0xcb15…a1a0 | For | 0 | 0.00% | — | 6mo ago |
| 4D0x4d4a…1bdf | For | 0 | 0.00% | — | 6mo ago |
07Forum
No forum thread is confidently linked to this proposal.