LDO - Reward Controller Access Request
01Summary
This proposal enables Lido DAO to distribute LDO token rewards across Aave v3 liquidity pools on Ethereum, Arbitrum, and Optimism by assigning the Emission_Admin role for LDO to Lido-controlled wallet addresses on each network. The Lido Liquidity Mining Committee will determine emission rates and durations on a rolling monthly basis.
- Type
- governance change
Key changes
- Assign Emission_Admin role for LDO token to Lido DAO-controlled address 0x87D93d9B2C672bf9c9642d853a8682546a5012B5 on Aave v3 Ethereum(high)
- Assign Emission_Admin role for LDO token to Lido DAO-controlled address 0x8C2b8595eA1b627427EFE4f29A64b145DF439d16 on Aave v3 Arbitrum(high)
- Assign Emission_Admin role for LDO token to Lido DAO-controlled address 0x5033823F27c5f977707B58F0351adcD732C955Dd on Aave v3 Optimism(high)
- Enable Lido Liquidity Mining Committee to determine LDO emission rates and duration on a rolling 30-day basis across the three Aave v3 deployments(high)
Generated by Kvorum
02Description
Simple Summary
This proposal is to enable Lido to distribute LDO rewards across the Aave v3 Ethereum, Arbitrum and Optimism Liquidity Pools. The Emission_Admin role for LDO on each network is to be assigned to a wallet controlled by the Lido DAO.
Abstract
Lido seeks to distribute LDO rewards across to the various Aave v3 deployments. To achieve this, the EmissionManager function assigns an owner to the Emission_Admin role for LDO on each respective Aave v3 deployment, [1,2].
The wallet with Emission Admin permission for LDO on each aave v3 deployment then controls the distribution of only LDO rewards across the respective Liquidity Pool.
Motivation
Enable Lido DAO to distribute LDO rewards across the Ethereum, Arbitrum and Optimism v3 Liquidity Pools.
The Lido Liquidity Mining Committee (LMC) determines the emission rate and duration at which LDO rewards are offered.
Typically, the LMC meets and determines the next 30 days of LDO rewards on a rolling basis. This means each month, the committee will determine if to extend the LDO rewards, or change the amount of LDO being offered across the various Aave v3 Liquidity Pools.
Specification
The EmissionManager, a governance controlled contract, assigns the Emission_Admin role for a specified token, LDO on each respective network.
The Emission_Admin role controls the distribution of the specified token, LDO, across the specified Aave deployment.
The Emission_Admin can distribute LDO anywhere across the Aave v3 Ethereum, Arbitrum and Optimism Liquidity Pool.
Implementation
Set Emission_Admin permission for LDO to the following Lido address:
Aave v3 Ethereum
- LDO Address Reward: 0x5A98FcBEA516Cf06857215779Fd812CA3beF1B32
- LDO Address Admin: 0x87D93d9B2C672bf9c9642d853a8682546a5012B5
Aave v3 Arbitrum
- LDO Address Reward: 0x13Ad51ed4F1B7e9Dc168d8a00cB3f4dDD85EfA60
- LDO Address Admin: 0x8C2b8595eA1b627427EFE4f29A64b145DF439d16
Aave v3 Optimism
- LDO Address Reward: 0xFdb794692724153d1488CcdBE0C56c252596735F
- LDO Address Admin: 0x5033823F27c5f977707B58F0351adcD732C955Dd
Test Cases
Arbitrum test cases can be found here.
Mainnet test cases can be found here.
Optimism test cases can be found here.
Payload Implementations
Arbitrum Payload Implementation can be found here.
Mainnet Payload Implementation can be found here.
Optimism Payload Implementation can be found here.
Deployed Payloads
Arbitrum Proposal Payload deployed address can be found here.
Mainnet Proposal Payload deployed address can be found here.
Optimism Proposal Payload deployed address can be found here.
Security Considerations
The proposal Payload was reviewed by Bored Ghost Developing.
Governance Considerations
Aave governance forum discussion and Snapshot vote.
References
- https://docs.aave.com/developers/guides/governance-guide/rewards#create-proposal
- https://github.com/aave/aave-v3-periphery/blob/master/contracts/rewards/interfaces/IEmissionManager.sol
- https://creativecommons.org/publicdomain/zero/1.0/
Copyright
Copyright and related rights waived via CC0, [3].
03Mismatch analysis
The proposal describes three parallel actions: setting the LDO Emission_Admin role to specific Lido-controlled wallets on Aave v3 Ethereum, Arbitrum, and Optimism, via payload contracts whose deployed addresses are explicitly listed (mainnet: 0x2636...ba1f; Arbitrum/Optimism: 0x2cbf...bd11f). The decoded calldata shows exactly three actions on mainnet: (0) a direct execute() call to the mainnet payload address matching the description, and (1)/(2) execute(address) calls to two distinct contracts, each passing the same L2 payload address 0x2Cbf7856f51660Aae066afAbaBf9C854FA6BD11f cited in the proposal's 'Deployed Payloads' section for Arbitrum and Optimism. This structure — mainnet payload executed directly, L2 payloads triggered via separate bridge/executor contracts on mainnet — is the standard Aave cross-chain governance execution pattern and is consistent with the proposal's stated intent, even though the specific bridge executor addresses (0x5f5c...6711 and 0x2e2b...05f1) are not named in the prose. This omission is routine implementation detail (mechanical bridging plumbing) rather than a substantive discrepancy, since the actual payload addresses being invoked match those disclosed in the proposal. I could not independently verify from the calldata alone that the internal logic of each payload assigns Emission_Admin to exactly the addresses listed (that logic lives inside the deployed payload contracts, referenced but not decoded here), so confidence is medium rather than high. No value, target, or scope mismatches were found between the prose and the decoded top-level actions.
Generated by Kvorum
04Actions
- Target
- 0x2636…ba1f
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
- Target
- 0x5f5c…6711
- Value
- 0 wei
- Function
- execute(address)
- Arguments
{ "0": "0x2Cbf7856f51660Aae066afAbaBf9C854FA6BD11f" }- Calldata
- Target
- 0x2e2b…05f1
- Value
- 0 wei
- Function
- execute(address)
- Arguments
{ "0": "0x2Cbf7856f51660Aae066afAbaBf9C854FA6BD11f" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- [ARFC] LDO Emission_Admin for Ethereum, Arbitrum and Optimism v3 Liquidity Pools ↗discourse · high confidence
Arguments for
- Lido supporting Aave growth through LDO rewards distribution is mutually beneficial for both protocols.— MarcZeller
- LDO incentives enhance Aave liquidity pools and attract additional capital to the protocol.— WintermuteGovernance
Arguments against
None surfaced.
Notable participants
- LlamaxyzProposer of the LDO Emission_Admin access request for Aave v3 liquidity pools.
- MarcZellerACI representative who explicitly endorsed the proposal as a win-win for both parties.
- WintermuteGovernanceDelegate who voiced full support for the proposal.
Generated by Kvorum
08Similar proposals
- aavecanceledOP Emission_Admin for Optimism v3 Liquidity Pool84%
- aaveexecutedOP Emission_Admin for Optimism v3 Liquidity Pool84%
- aaveexecutedAssign Emission Admin - Ethereum, Arbitrum and Optimism81%
- aaveexecutedSet LDO, stMATIC, MaticX and SD Emission_Admin for Polygon v3 Liquidity Pool81%
- aavedefeatedSet LDO, stMATIC, MaticX and SD Emission_Admin for Polygon v3 Liquidity Pool81%
- aaveexecutedSet Liquidity Observation Labs as Emission manager for wstETH on V3 markets76%
- lidoexecutedOmnibus vote: 1) Send 300,000 LDO tokens from Treasury to the Token Manager 0xf73a1260d222f447210581DDf212D915c09a3249;65%
- lidoactiveOmnibus vote: 1) Send 300,000 LDO tokens from Treasury to the Token Manager 0xf73a1260d222f447210581DDf212D915c09a3249;65%
- lidoexecutedOmnibus vote: 1) Set lido.eth to resolve to Lido smart contract 0xae7ab96520de3a18e5e111b5eaab095312d7fe84;2) Allocate 5,000 LDO tokens to Jacob Blish Nov 2021 compensation;3) Allocate 3,000 LDO Isid…64%
- lidoactiveOmnibus vote: 1) Send 300,000 LDO tokens from Treasury to the Token Manager 0xf73a1260d222f447210581DDf212D915c09a3249;63%