[EP 5.14] [Executable] Endowment permissions to karpatkey - Update #4
Abstract
This proposal aims to introduce new permissions for deploying Endowment funds, focusing on improved diversification and alignment with the evolving market landscape and liquidity. We are also introducing an independent audit report together with the Permissions Update; this will be the standard practice for Permissions Updates going forward.
Motivation
Effective treasury management strategies must be adapted to market conditions and protocol updates; for existing Permissions, there might be migrations and introductions of new pools; for new Permissions, protocols and pools that were previously considered immature and unsuitable for the Endowmentās risk appetite may become viable options as they become more time- and battle-tested. This proposal seeks to request new permissions from the ENS DAO for karpatkey, enabling the introduction of new yield-generation strategies for the Endowment.
The new permissions have also been audited byĀ ThirdGuard, an independent 3rd-party, to ensure the suggested changes have been thoroughly reviewed by a technically-competent, independent party.
Specification
New permissions implemented in this payload
- Deposit osETH on Aave v3;
- Stake (and unstake) ETH on Stakewise v3. Through theĀ Genesis Vault.
- Mint (and burn) osETH on Stakewise v3. Through the Genesis Vault.
- WETH/osETH pool on Balancer;
- WETH/osETH pool on Aura Finance;
- Swaps:
- WETH <> osETH on Balancer
- USDC <> osETH on Uniswap v3
- USDC <> WETH <> osETH on CoW Swap
- RPL <> WETH on Uniswap v3
- RPL <> WETH on CoW Swap
- Unsign order on Cow Protocol so that a pending order that has been submitted but not executed can be cancelled.
Additional implementation details
- The enableModule(address module) function is called to enable the modules, pointing it to theĀ Avatar addressĀ (the Endowment).
- The payload to be executed upon the successful approval of this proposal can be foundĀ here. The proposed permissions policy can be visualised in the aforementionedĀ linkĀ for ease of review.
- We have tested the payload to make sure all interactions mentioned on this proposal work as expected through ourĀ Test Safe.
- With the introduction of theĀ new Roles App Permissions Visualisation tool, manually updating the āPreset Permissions - ENS EndowmentāĀ documentĀ is no longer necessary. The new tool provides an up-to-date and accurate method for exploring the current permissions granted to karpatkey by the ENS DAO.
Auditing process
Introduction of an independent audit report
We have received feedback in the previous proposal that independent, 3rd party code review would be helpful for the ENS community and delegates to make a more informed decision and to reduce delegate fatigue.
In our commitment to transparency and effort towards DAO efficiency, karpatkey decided to engage with independent, third-party firms / individuals for every contract upgrade starting with this proposal.Ā ThirdGuardĀ has been engaged for this proposalās code review; ThirdGuard is a provider of on-chain risk monitoring solutions, and has been working with the Zodiac Roles Modifier since its inception (and its precursor, Scope Guard). Given their past experiences across Zodiac Roles Modifier, Solidity, and DeFi risk management, ThirdGuard was deemed to be a suitable candidate to fulfil the role of policy reviewer. Their approach to auditing the permissions can be foundĀ here.
The ThirdGuard audit for the permissions in this payload can be foundĀ here.
Audit report summary is as follows:
- No material findings were found.
- Policy changes requested were considered bona fide actions needed by the Manager to carry out their DeFi operations.
- 1 Informational Finding and 1 Warning were logged, and acknowledged by karpatkey. These findings do not post an immediate risk but are relevant to security best practices.
