Set REZ, KERNEL and rsETH Emission Admin to ACI
01Summary
This proposal grants ACI (Aave Grants DAO) the emission admin role for KERNEL, REZ, and rsETH tokens on Aave v3 Core and Prime instances, enabling ACI to distribute these rewards to incentivize deposits of rsETH and ezETH and drive adoption of these liquid staking tokens.
- Type
- governance change
Key changes
- Grant emission admin role for KERNEL token to ACI (0xdef1FA4CEfe67365ba046a7C630D6B885298E210) on Aave v3 Core and Prime instances(high)
- Grant emission admin role for REZ token to ACI (0xdef1FA4CEfe67365ba046a7C630D6B885298E210) on Aave v3 Prime instance(high)
- Grant emission admin role for rsETH token to ACI (0xdef1FA4CEfe67365ba046a7C630D6B885298E210) on Aave v3 Core and Prime instances(high)
Generated by Kvorum
02Description
Simple Summary
This proposal enables ACI to distribute REZ, KERNEL and rsETH rewards across several instances of Aave v3.
Motivation
The Kelp team proposes distributing rsETH and KERNEL rewards on Core and Prime instances of Aave v3 to incentivize rsETH deposits and drive adoption. Similarly, the Renzo team seeks to distribute REZ rewards across Prime instance of Aave v3 to support the growth of ezETH deposits.
Both teams aim to leverage these rewards to foster the continued adoption and expansion of rsETH and ezETH within the Aave ecosystem. The ACI team will manage the distribution of rewards on behalf of Kelp and Renzo.
Specification
Aave Core & Prime:
The emission admin role for KERNEL, REZ and rsETH is granted to 0xdef1FA4CEfe67365ba046a7C630D6B885298E210.
References
- Implementation: AaveV3Ethereum
- Tests: AaveV3Ethereum
- Snapshot: Direct-to-AIP
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal follows the standard Aave v3 governance payload pattern: the on-chain action is a single delegatecall-style execute() invocation on a dedicated payload contract, matching the linked implementation contract (AaveV3Ethereum_SetREZKERNELAndRsETHEmissionAdminToACI). The decoded calldata does not expose the internal function calls made by that payload contract (e.g., the individual setEmissionAdmin calls for KERNEL, REZ, and rsETH to the specified ACI address), so it is not possible to directly verify the three specific admin-grant claims against the calldata at this level of decoding. However, the target address, chain, zero value, and 'execute()' signature are all consistent with a legitimate Aave payload execution as referenced in the proposal's Implementation link, and there is no evidence of any conflicting or additional action. Given the opacity of the single execute() call, confidence in a full line-by-line verification is low, but nothing in the visible calldata contradicts the description, so the assessment is 'consistent' with low confidence rather than flagging an unsubstantiated discrepancy.
Generated by Kvorum
04Actions
- Target
- 0x302f…6db5
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedSet ACI as Emission Manager for USDS, aUSDS and awstETH75%
- aaveexecutedEURe Emissions Manager73%
- aaveexecutedSet ACI as Emission Manager for Aave Liquidity Mining programs73%
- aaveexecutedSet ACI as Emission Manager for wstETH & tBTC72%
- aaveexecutedSet Aave Chan Initiative as Emission Manager for fdUSD on BNB Chain Aave V369%
- aaveexecutedMainnet PYUSD Emissions Admin69%
- aaveexecutedSet ACI as Emission Manager on the Avalanche network69%
- aaveexecutedACI Phase IV – “Road to 80”68%
- aaveexecutedOptimism susd Emission Admin68%
- aaveexecutedACI Service Provider Proposal67%