KVORUM
aaveSource: Aave governance v3 · #39

Set Liquidity Observation Labs as Emission manager for wstETH on V3 markets

executedMar 4, 2024, 04:27 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Grants Lido Liquidity Observation Labs the ability to manage incentive emissions for wstETH tokens across Aave V3 markets on Ethereum, Base, Arbitrum, Optimism, and Polygon, enabling them to fund incentive programs to drive user growth and market activity.

Type
governance change

Key changes

  • Set Lido Liquidity Observation Labs wallet (0xC18F11735C6a1941431cCC5BcF13AF0a052A5022) as the emission admin for wstETH token on Ethereum, Base, Arbitrum, Optimism, and Polygon Aave V3 markets(high)
  • Lido Liquidity Observation Labs gains authority to define and fund incentive programs for wstETH markets across multiple networks(high)
  • Gnosis chain excluded from this AIP per Lido Liquidity Observation Labs request to not favor bridged stETH in the short term(medium)
ContractsEMISSION_MANAGER on EthereumEMISSION_MANAGER on BaseEMISSION_MANAGER on ArbitrumEMISSION_MANAGER on OptimismEMISSION_MANAGER on Polygon
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

273 words

Simple Summary

This ARFC proposes to set the Lido Liquidity Observation Labs' wallet as the emission manager for the wstETH token on Ethereum, Base, Arbitrum, Optimism and Polygon Aave V3 markets. This will enable the Lido Liquidity Observation Labs to define and fund incentive programs for all wstETH markets, promoting growth and expanding the user base of Aave.

Motivation

The Lido "Liquidity Observation Labs" has expressed a desire to actively contribute to the growth and development of Aave V3. By setting their wallet as the emission manager for the wstETH token, theY will be able to directly fund incentive programs that can attract more users to the protocol and stimulate activity. This aligns with the broader goals of the Aave community to foster active and engaged markets.

Specification

The Lido Liquidity Observation Labs safe wallet use the same address on all networks: 0xC18F11735C6a1941431cCC5BcF13AF0a052A5022 The AIP calls EMISSION_MANAGER.setEmissionAdmin(asset, admin) for each network. With wstETH as the asset and the Lido Liquidity Observation Labs' safe address as the admin. This method will set the Lido Liquidity Observation Labs wallet as the emission admin for the wstETH token on Ethereum, Base, Arbitrum, Optimism and Polygon V3 markets. After synchronizing with the Liquidity Observation Labs, it was decided not to favor, in the short term, the bridged version of stETH on the gnosis chain. As such, and following their request, no role will be attributed on the gnosis chain in the context of this AIP.

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The proposal follows the standard Aave governance pattern: the on-chain action is a single execute() call on a payload contract deployed on Ethereum mainnet, with no further decoded arguments exposed at this level. This is typical for BGD Labs-style multi-network AIPs, where the payload contract internally calls EMISSION_MANAGER.setEmissionAdmin(wstETH, admin) on Ethereum directly and dispatches equivalent cross-chain governance messages to Polygon, Optimism, Arbitrum, and Base. Because the decoded calldata does not unpack the internal logic of the payload contract, I cannot directly verify the specific asset, admin address, or per-network calls described in the prose. However, nothing in the available calldata contradicts the description, and the pattern (single execute() call linked to network-specific payload contracts referenced in the 'Implementation' links) is consistent with how such proposals are typically structured. No value mismatches, target mismatches, or omitted/extra actions can be identified given the information available. Given the lack of visibility into the payload's internal calls, confidence is medium rather than high, but there is no basis to flag a discrepancy.

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
0xdd59…ba32
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

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.