[RFC] Launch DAO Managed "Indexed" Vaults on the Lazy Summer Protocol

General Discussion Request for Comment [RFCs]
, ,
13

Thanks to everyone here for the feedback and discussion. And especially thanks to @BlockAnalitica for their proposal of the risk Framework.

What I’d like to do here is put down a proposal for the next steps and to gain alignment around initial vault (not arks) parameters to ensure as a DAO we are aligned and we can then proceed with the first votes this Wednesday 28th Jan.

In summary, I would like to propose we move forward with the setup and creation of the DAO Managed Vaults in order to launch them at the earliest opportunity.

Risk Framework
Move BlockAnalitica Framework Proposal to SIP for the upfront 25,000 USDC payment to create the Risk Framework needed for the DAO Managed Vaults.

Key Vault Params

  • Vault Fee’s → I would like to propose that these Vaults have the same Vault Fee’s as the actively managed vaults (1% stables, 0.3% volatile) however with a different expense structure;

    • Proposed tip streams (expenses as a % of income from fees);
      • Summer.fi (Labs Co) via the Foundation: 30% (Same as the current vaults) to continue to cover costs to operate the UI, associated infrastructure and various costs associated with marketing and growth.
      • BlockAnalitica: 5%, as proposed in their Risk Framework
      • Guardians: 15% - I think these vaults serve as a good place to pay the DAO approved guardians for their ongoing work, which on these vaults, will serve as the first line of defence of any issues
      • This leaves 50% of the fee to be used by the protocol, which I propose goes firstly towards the existing referral and integration costs already approved by the DAO, but accepting these vaults into it too → and then the rest to the DAO, forming part of the SUMR token holder revenue share.

  • Keepers → I propose the same keepers are enabled as the existing Actively Managed Vaults, currently operated by Summer.fi and under address: 0xc2a8467a52Fec8383c424149000cf384de9Ba1B5

  • Guardian Role → I propose adding the Guardian role to the Vaults, ensuring it can pause all markets if required. Members of the guardian role currently under discussion here: [RFC] Establish Guardian Module & Emergency Risk Controls

    • I propose that the Vaults should not be activated until a guardian multisig is approved and live from the DAO.
    • I also propose that a new function is established within the DAO Managed Vaults/Arks that allow the Guardians to set the DepositCaps to any ark market to 0 in the event of a market event with any of the supported protocols or markets. The Guardians should not have any other Risk Manager roles, and it should only be up to the DAO to re-enable a positive depositCap after the Guardian has set it to 0. No other parameters should be given to the Guardian beyond the existing pauses etc.

Timings

28-Jan-26

  • Promote BA Risk Framework to SIP

Week of 2-Feb-26

  • Deploy Vaults to the following chains;
    • Base - USDC / ETH
    • Ethereum - USDC / ETH
  • Initial Arks proposed to the forum (without risk params) for deployment the following week

Week of 9-Feb-26

  • Agree the initial arks risk params as per the new Risk Framework
  • Deploy first arks
  • Aim to have Guardians live, or at minimum proposed too
  • Promote to SIP the onboarding and first set of risk params of new markets

Week of 16-Feb-26

  • Go live with DAO Managed Vaults and the first arks

Tagging @Recognized_Delegates here for your feedback on plans.

Unless any major concerns raised, I will promote to SIP later on Tuesday the vote for the BA Framework Proposal.

6 Likes
[SIP0.2] Establish Guardian Module & Emergency Risk Controls