Should Aave add the audited claimRewardsToSelf function to the liquidity mining incentives contract?
Summary Aave incentive contracts currently only contain claiming functions in which the caller specifies the recipient to address, who will receive the claimed rewards. Unfortunately, this poses a security problem for abstractly-designed smart contract claimants that do not have fully-trusted originators of claiming txs. This is the case for Enzyme vaults. By adding an additional claiming function to the incentive contract that uses msg.sender instead of to, the tx originator no longer needs to be trusted. This simple addition - that can reuse the exact same claiming logic as the current claiming functions and will not require any changes to storage layout - will increase composability opportunities with Enzyme and similarly architected protocols.
Background Enzyme is a decentralised asset management infrastructure built on Ethereum. It allows asset managers to build on-chain investment Vaults that utilise and allocate to the newest innovations in DeFi. Because all transactions occur on the Ethereum blockchain, compliance, accounting, and investor management services are rendered programatically and at a dramatically-reduced cost to their traditional finance counterparts. Amongst other things, Enzyme Vaults can interact with AAVE by lending. We are currently also working on accommodating the borrowing functionality to enable leveraged strategies as part of our Sulu release this quarter. In order to keep providing our users with superior asset management tools in DeFi, we want to open up the liquidity mining option for them as soon as possible. Our users rely on having the latest DeFi functionality in Enzyme to reach their full potential.
Proposal Add function claimRewardsToSelf(address[] calldata assets, uint256 amount) to the liquidity mining incentives contract, which reuses the logic of claimRewards() but uses msg.sender instead of to
Benefits for AAVE
- Increased AAVE adoption by the Enzyme user base and other similarly architected protocols
- Tapping into a new and fast-growing community
- A closer collaboration between our two projects & communities
- Enzyme contracts have been audited by PWC, Chain Security and some of the leading auditors in the space who sit on the Enzyme Council
- Opening up the possibility for new and novel use-cases to be built around AAVE
Preview Summary Aave incentive contracts currently only contain claiming functions in which the caller specifies the recipient to address, who will receive the claimed rewards. Unfortunately, this poses a security problem for abstractly-designed smart contract claimants that do not have fully-trusted originators of claiming txs. This is the case for Enzyme vaults. By adding an additional claiming function to the incentive contract that uses msg.sender instead of to, the tx originator no longer needs to be trusted. This simple addition - that can reuse the exact same claiming logic as the current claiming functions and will not require any changes to storage layout - will increase composability opportunities with Enzyme and similarly architected protocols.
Background Enzyme is a decentralised asset management infrastructure built on Ethereum. It allows asset managers to build on-chain investment Vaults that utilise and allocate to the newest innovations in DeFi. Because all transactions occur on the Ethereum blockchain, compliance, accounting, and investor management services are rendered programatically and at a dramatically-reduced cost to their traditional finance counterparts. Amongst other things, Enzyme Vaults can interact with AAVE by lending. We are currently also working on accommodating the borrowing functionality to enable leveraged strategies as part of our Sulu release this quarter. In order to keep providing our users with superior asset management tools in DeFi, we want to open up the liquidity mining option for them as soon as possible. Our users rely on having the latest DeFi functionality in Enzyme to reach their full potential.
Proposal Add function claimRewardsToSelf(address[] calldata assets, uint256 amount) to the liquidity mining incentives contract, which reuses the logic of claimRewards() but uses msg.sender instead of to
Benefits for AAVE Increased AAVE adoption by the Enzyme user base and other similarly architected protocols Tapping into a new and fast-growing community A closer collaboration between our two projects & communities Enzyme contracts have been audited by PWC, Chain Security and some of the leading auditors in the space who sit on the Enzyme Council Opening up the possibility for new and novel use-cases to be built around AAVE
| Voter | Cast Power | Vote & Rationale |
|---|---|---|
 0x458c...21730E | 10,000 | Yes |
 0x9824...dEA969 | 442 | Yes |
 0xf6Be...31e84D | 422 | Yes |
 gekko.eth 🦇🔊 | 301 | Yes |
 0x6001...4d887a | 161 | Yes |
VOTE POWER
Proposal Status
- Sat October 16 2021, 06:30 amVoting Period Starts
- Thu October 21 2021, 06:30 amEnd Voting Period
Current Results
1-Yes
11,729.666
2-No
71.901