KVORUM
aaveSource: Aave governor v2 · #180

OP Emission_Admin for Optimism v3 Liquidity Pool

canceledMar 19, 2023, 09:34 AM UTCby550x55b1…f262

01Summary

AISummary by Kvorumclaude-haiku-4-5

Lido DAO proposes to receive the Emission_Admin role for OP tokens on Optimism, enabling it to distribute OP rewards across the Aave v3 Optimism Liquidity Pool. The Lido Liquidity Mining Committee will determine monthly emission rates and durations for OP rewards as part of bootstrapping wstETH adoption on Optimism.

Type
governance change

Key changes

  • Transfer Emission_Admin role for OP token on Optimism from Optimism team to Lido DAO(high)
  • Enable Lido DAO to distribute OP and LDO rewards across Aave v3 Optimism deployment(high)
  • Grant Lido Liquidity Mining Committee authority to determine monthly OP emission rates and duration(medium)

Notable concerns

  • Monthly rolling determination of emission rates creates ongoing governance requirement
  • Emission Admin role grants broad discretion to distribute OP anywhere across Aave v3 on Optimism
Contracts0x5f5c02875a8e9b5a26fbd09040abcfdeb2aa67110x4b8D3277d49E114C8F2D6E0B2eD310e29226fe160x42000000000000000000000000000000000000420x5033823F27c5f977707B58F0351adcD732C955Dd
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

325 words

Summary

This proposal is to enable Lido DAO to distribute OP rewards across the Aave v3 Optimism Liquidity Pool.

The Emission_Admin role for OP on Optimism is currently assigned to the Optimism team and is to be transferred to Lido DAO.

Abstract

Lido DAO seeks to distribute OP rewards across to the Aave v3 Optimism deployment. To achieve this, the EmissionManager function reassigns an owner to the Emission_Admin role for OP.

The wallet with Emission Admin permission for OP then controls the distribution of OP and LDO rewards on the Optimism Liquidity Pool. This proposal will enable LDO and OP rewards to be distributed across the Optimism v3 deployment.

Motivation

Lido DAO has received a grant nominated in OP tokens that are to be used for bootstrapping the adoption of wstETH on the Optimism network. A portion of these rewards are to be distributed on the Aave v3 deployment.

The Lido Liquidity Mining Committee (LMC) will be determining the emission rate and duration that OP rewards are offered on the Aave v3 deployment.

Typically, the LMC meets and determines the next 30 days rewards to be distributed on a rolling basis. This means each month, the committee will determine if to extend the OP rewards, or change the amount of OP being offered across the Aave v3 Liquidity Pools on Optimism.

Specification

The EmissionManager, a governance controlled function, assigns the Emission_Admin role for a specified token, OP, on each respective network.

The Emission_Admin role controls the distribution of the specified token, OP, across the specified Aave deployment.

The Emission_Admin can distribute OP anywhere across the Aave v3 on the Optimism Liquidity Pool.

Emission Admin: 0x5033823F27c5f977707B58F0351adcD732C955Dd

Implementation

setEmissionAdmin(address reward, address admin)

OP Address Reward: 0x4200000000000000000000000000000000000042

OP Address Admin: 0x5033823F27c5f977707B58F0351adcD732C955Dd

The relevant links for this proposal are shown:

The proposal Payload was reviewed by Bored Ghost Developing.

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal description matches the well-known Aave governance pattern for cross-chain payload execution: an L1 'execute(address)' call routes to a payload contract that performs the actual setEmissionAdmin(reward, admin) call on Optimism. The single decoded action here only shows the outer execute(address) call and the payload contract address — it does not expose the internal calldata (reward token address, admin address) that the payload contract will execute on L2. Because of this, I cannot directly verify that the payload's internal call sets OP's Emission_Admin to the exact address (0x5033823F27c5f977707B58F0351adcD732C955Dd) stated in the description, nor confirm the OP token address used. This is a routine and expected abstraction for this proposal type (referenced test files and payload implementation links corroborate the described behavior), so there is no evidence of a mismatch. However, since the actual parameters are not visible in the decoded calldata provided, confidence in this comparison is low. No value, target, or omission discrepancies are evident from the available data.

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
#0execute(address)chain 0x1
Target
0x5f5c…6711
Value
0 wei
Function
execute(address)
Arguments
{
  "0": "0x4b8D3277d49E114C8F2D6E0B2eD310e29226fe16"
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total
Filter:
VoterChoice% of totalRationale
B80xb83b…cf5cFor80.2K0.00%—4y ago
B90xb933…8dd1For41.7K0.00%—4y ago
160x1664…36d9For16.9K0.00%—4y ago
E20xe266…43a0For2.20.00%—4y ago
890x89d9…8978For1.10.00%—4y ago
880x8824…5443For0.50.00%—4y ago
420x4229…9006For0.30.00%—4y ago
030x03ba…a1a1For0.10.00%—4y ago
AB0xabf4…5e23For00.00%—4y ago
Showing 9

07Forum

No forum thread is confidently linked to this proposal.