# \[SIP0.2\] Establish Guardian Module & Emergency Risk Controls

**URL:** <https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675>\
**Category:** Summer Improvement Proposals \[SIPs\]\
**Tags:** sip0, risk, guardians, emergency, control\
**Created:** [January 30, 2026, 5:53pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675 "2026-01-30T17:53:08Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jensei](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/jensei/32/69_2.png) [@jensei](https://forum.summer.fi/u/jensei)\
**Post date:** [January 30, 2026, 5:53pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/1 "2026-01-30T17:53:08Z")

</div>

### 1. Overview:

This SIP proposes establishing a **Guardian Module** for the Lazy Summer Protocol: a narrowly scoped, community-controlled multisig empowered to take **temporary emergency actions** during high-severity risk events, reducing loss amplification while preserving DAO sovereignty.

> _ **RFC:** [[RFC] Establish Guardian Module & Emergency Risk Controls](https://forum.summer.fi/t/rfc-establish-guardian-module-emergency-risk-controls/613)_

* * *

### 2. Motivation:

The Guardian Module introduces a **minimal, accountable safety layer** aligned with best practices used by Compound, ENS, Arbitrum, and others designed to:

- act faster than governance,
- operate only under explicit emergency conditions,
- and remain fully accountable to the DAO.

> _This SIP does **not** centralize power or replace risk management. It reduces loss amplification, not risk existence._

* * *

### 3. Specification:

#### 3.1 Guardian Module Overview

The Guardian Module will be implemented as a **multisig** with strictly limited emergency authorities.

**Authorized actions (only):**

1. **Vault Pause**  
_Temporarily halt deposits and withdrawals on affected DAO-managed vaults._

2. **Deposit Cap Override**  
_Set deposit caps to `0` for DAO risk-managed vaults._

3. **Governance / Onchain Proposal Cancellation**  
_Cancel in-flight proposals that pose immediate protocol risk._

> _The Lazy Summer Protocol has `regular` and `with expiry date` guardians. Only the latter can cancel proposals - as long as they are not expired._

**Explicit limitations:**

- No proactive parameter tuning
- No fund movement
- No strategy onboarding/offboarding
- Reactive use only

**All actions are:**

- fully transparent,
- time-bounded,
- subject to mandatory post-incident DAO review.

#### 3.2 Emergency Trigger Thresholds

Guardians may exercise authority **only when one or more** of the following conditions are met:

- **≥ 4% realized or projected loss** at a fleet or ark level
- Active exploit or credible exploit in progress
- Severe oracle failure or critical dependency outage
- External protocol failure materially impacting vault safety

> _Thresholds are intentionally conservative to allow earlier intervention than DAO voting cycles._

#### 3.3 Guardian Composition & Signing Rules

**Proposed multisig configuration:**

- **8 signers**
- **6/8 signing threshold (75%)**
- **180d expiration** , renewable via governance

**Initial Guardian Set (proposed):**

- @blockful
- @Meta
- @Raphael_Anode
- @halaprix
- @MasterMojo
- @jensei
- @JavierD
- @chrisb

> _To confirm the initial set of guardians I request all the above mentioned users to confirm, accept the responsibilities and post their wallet address to be included in the guardian multi-sig in the comment below this post._

This set reflects:

- risk & governance expertise,
- operational readiness,
- diversity of affiliations,
- prior public accountability.

> _A subjective assessment of member selection is included to align with [L2BEAT Security Council standards](https://medium.com/l2beat/stages-update-security-council-requirements-4c79cea8ef52), and can be found [here](https://docs.fileverse.io/0x6d7f3e4fd1ac02a158496a4606fc35d6650c1c40/2#key=n4wOj_SZr1_S5wLaEzdzJlDGGLrIYNEMTsJ5FEWCLJzehaWiWAHBZQSIX2z_wnCK)._

#### 3.4 Guardian Responsibilities

Guardians are expected to:

- remain highly responsive during incidents,
- act strictly within defined authority,
- coordinate with @BlockAnalitica, SEAL Org, Lazy Summer Foundation, and the DAO,
- publish or contribute to post-incident transparency reports,
- accept public accountability for actions taken.

**Failure to meet expectations may result in removal via governance.**

#### 3.5 Contracts & Transactions

```auto
	`function grantGuardianRole(address account)`

	`function setGuardianExpiration(
		address account,
		uint256 expiration`

```

_on all supported chains_

```auto
    "protocolAccessManager": {
      "base": "0xf389BCEa078acD9516414F5dabE3dDd5f7e39694",
      "mainnet": "0xf389BCEa078acD9516414F5dabE3dDd5f7e39694",
      "arbitrum": "0xf389BCEa078acD9516414F5dabE3dDd5f7e39694",
      "sonic": "0xAFb8a8beA8F7CdB4b65437b0c5963dc7Cd270bC6",
      "hyper": "0x38fB5a7fa70103dCd9e8A969f3975A77E0fE755f"
    },

```

_where_

```auto
/// @notice Minimum allowed guardian expiration period (7 days)
uint256 public constant MIN_GUARDIAN_EXPIRY = 7 days;

/// @notice Maximum allowed guardian expiration period (180 days)
uint256 public constant MAX_GUARDIAN_EXPIRY = 180 days;

```

#### 3.6 Compensation

To align incentives and accountability:

- **15% of DAO-managed vault income** allocated to a Guardian compensation pool
  - Split evenly across active signers
  - Distributed only while Guardian powers are active
  - as soft-proposed: [**here**](https://forum.summer.fi/t/rfc-launch-dao-managed-indexed-vaults-on-the-lazy-summer-protocol/601/13).

In addition, the DAO may approve:

- **Supplementary SUMR emissions** (subject to separate confirmation or future SIP)

* * *

### 4. Risk Assessment

**Risks:**

- Centralization of emergency power
- Guardian inactivity or capture
- Governance capture preventing renewal

**Mitigations:**

- Narrow, enumerated powers only
- High multisig threshold (75%)
- Annual expiration & DAO renewal
- Full transparency & post-event review

> _Upon confirmation from the proposed individual entities, I will create and share a multi-sig in the comment below; pre-onchain vote publishing._

* * *

### 5. Voting

> If **YES:** - Approves creation of the Guardian Module, authorizes deployment of contracts, confirms initial Guardian set, and activates emergency authorities under defined thresholds.

> If **NO:** - Maintains current governance-only emergency posture.

* * *

Tagging all [@Recognized\_Delegates](https://forum.summer.fi/groups/recognized_delegates) for review, before it is posted for an onchain vote ~04/02/2026.

---

<div class="post-metadata">

**Author:** ![JavierD](https://avatars.discourse-cdn.com/v4/letter/j/ebca7d/32.png) [@JavierD](https://forum.summer.fi/u/JavierD)\
**Post date:** [February 1, 2026, 11:25am UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/2 "2026-02-01T11:25:02Z")

</div>

I’m happy to accept my role as Guardian, and I’m really looking forward to the DAO-managed vaults.  
Wallet address: `0xcA4Bc5E1564EBdC2b7e2C9e498735860668A807f`

---

<div class="post-metadata">

**Author:** ![chrisb](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/chrisb/32/28_2.png) [@chrisb](https://forum.summer.fi/u/chrisb)\
**Post date:** [February 2, 2026, 12:21pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/3 "2026-02-02T12:21:29Z")

</div>

I’m happy to accept my role as Guardian

Wallet address: `0xe9c245293dac615c11a5bf26fcec91c3617645e4` (chrisb.eth)

---

<div class="post-metadata">

**Author:** ![halaprix](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/halaprix/32/13_2.png) [@halaprix](https://forum.summer.fi/u/halaprix)\
**Post date:** [February 2, 2026, 1:55pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/4 "2026-02-02T13:55:02Z")

</div>

I accept the role, my signer : `0x718b75a546a1b7edf107199aaa62dc257cb7ee80`⁩ ☮

---

<div class="post-metadata">

**Author:** ![MasterMojo](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/mastermojo/32/8_2.png) [@MasterMojo](https://forum.summer.fi/u/MasterMojo)\
**Post date:** [February 2, 2026, 2:45pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/5 "2026-02-02T14:45:14Z")

</div>

I accept my role as Guardian.

wallet: 0xF68D2BfCecd7895BBa05a7451Dd09A1749026454 (MassterMojo.eth)

---

<div class="post-metadata">

**Author:** ![blockful](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/blockful/32/439_2.png) [@blockful](https://forum.summer.fi/u/blockful)\
**Post date:** [February 2, 2026, 4:01pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/6 "2026-02-02T16:01:01Z")

</div>

I accept my role as Guardian.

wallet: `0x1F3D3A7A9c548bE39539b39D7400302753E20591`(`gov.blockful.eth`)

---

<div class="post-metadata">

**Author:** ![Raphael\_Anode](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/raphael_anode/32/476_2.png) [@Raphael\_Anode](https://forum.summer.fi/u/Raphael_Anode)\
**Post date:** [February 3, 2026, 10:20am UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/7 "2026-02-03T10:20:44Z")

</div>

Happy to accept my role as a Guardian.

As an address please use: `0x6ad64B3B5300821b651aF5415c2119a6ED4e2007`

---

<div class="post-metadata">

**Author:** ![jensei](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/jensei/32/69_2.png) [@jensei](https://forum.summer.fi/u/jensei)\
**Post date:** [February 3, 2026, 1:27pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/8 "2026-02-03T13:27:31Z")

</div>

I accept my role as Guardian.

wallet: `0x746bb7beFD31D9052BB8EbA7D5dD74C9aCf54C6d`(`jensei.eth`)

---

<div class="post-metadata">

**Author:** ![Sixty](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/sixty/32/115_2.png) [@Sixty](https://forum.summer.fi/u/Sixty)\
**Post date:** [February 3, 2026, 2:55pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/9 "2026-02-03T14:55:44Z")

</div>

I would like to make a suggestion here: Adding a regular liveness check to test the operational readiness of the Guardian module by verifying the availability of keys and the responsiveness of GM members, including the effectiveness of coordination.

This could be as simple as creating and signing an empty transaction every month / 3 months, and sharing how long it took to reach the 6/8 threshold and 8/8 threshold. Obviously results here could be skewed due to coordination around the liveness check. But maybe a [proposer](https://help.safe.global/en/articles/235770-proposers) could be added to the multisig, who randomly decides when the liveness check happens, which maintains security while maintaining the integrity of the test. Allowing for a more realistic simulation of an emergency / exploit.

---

<div class="post-metadata">

**Author:** ![chrisb](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/chrisb/32/28_2.png) [@chrisb](https://forum.summer.fi/u/chrisb)\
**Post date:** [February 3, 2026, 9:18pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/10 "2026-02-03T21:18:16Z")

</div>

I am very much for the liveness check, and was something was discussed with @jensei and @halaprix recently too.

I also like the idea of an external proposer being added to create this periodic check.

---

<div class="post-metadata">

**Author:** ![jensei](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/jensei/32/69_2.png) [@jensei](https://forum.summer.fi/u/jensei)\
**Post date:** [February 4, 2026, 2:18pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/11 "2026-02-04T14:18:55Z")

</div>

thank you all for confirming and accepting your role as Guardians. We are still missing @Meta’s confirmation and I did not hear back for couple of days - I would like to supplementary nominate @Sixty, @TokenBrice, and @Thomas. As we only need one more signer, I would suggest to consider the other two community members to be considered in future when a rotation of guardians would be needed

secondly, I do agree with @Sixty comment on the liveness check and also considering adding a proposer who randomly decides on the timing of the check

---

<div class="post-metadata">

**Author:** ![Sixty](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/sixty/32/115_2.png) [@Sixty](https://forum.summer.fi/u/Sixty)\
**Post date:** [February 4, 2026, 2:24pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/12 "2026-02-04T14:24:00Z")

</div>

Hey @jensei, happy to accept the nomination for the guardian role.

Wallet address: 0x84bC99d6067f30E01e32D7E7E193d68E24546EcC

---

<div class="post-metadata">

**Author:** ![Thomas](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/thomas/32/431_2.png) [@Thomas](https://forum.summer.fi/u/Thomas)\
**Post date:** [February 4, 2026, 2:36pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/13 "2026-02-04T14:36:15Z")

</div>

Hi @jensei, I think since @Sixty already accepted the role, you have the necessary signers.  
But you can consider me as back up if a rotation of guardians is necessary.

0xF523EEc9E35a697E5bc3e3534167BE9bAdB68e2D

---

<div class="post-metadata">

**Author:** ![jensei](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/jensei/32/69_2.png) [@jensei](https://forum.summer.fi/u/jensei)\
**Post date:** [February 4, 2026, 2:39pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/14 "2026-02-04T14:39:51Z")

</div>

@blockful @Raphael_Anode @halaprix @MasterMojo @JavierD @chrisb

* * *

thank you @Sixty for accepting your nomination and stepping in!

I have deployed and activated the [multisig](https://app.safe.global/home?safe=base:0x91E4482CF58aC14d8DC25290d828b2A4D9492BA4) with 6/8 ruleset across Base, Ethereum, Arbitrum, Sonic, and HyperEVM networks at [tx](https://basescan.org/tx/0xb810ecff092262a29a5969bd7b2467fdd192c6153c3bdc28941840348aab15ed).

* * *

additionally thank you @Thomas for stepping in as a backup! much appreciated

---

<div class="post-metadata">

**Author:** ![jensei](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/jensei/32/69_2.png) [@jensei](https://forum.summer.fi/u/jensei)\
**Post date:** [February 5, 2026, 1:33pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/15 "2026-02-05T13:33:30Z")

</div>

VOTE:

> **[Tally | Lazy Summer DAO (Official) - V2 | SIP0.2: Grant Guardian Roles](https://gov.summer.fi/dao/proposal/108093388136831773407292946235331649189762991144555290509377111240682330256900)**
>
> SIP0.2: Grant Guardian Roles

---

<div class="post-metadata">

**Author:** ![Meta](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/meta/32/316_2.png) [@Meta](https://forum.summer.fi/u/Meta)\
**Post date:** [February 5, 2026, 6:46pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/16 "2026-02-05T18:46:52Z")

</div>

I remain interested in the Guardian role, and feel strongly that having a representative deeply aligned with depositors would be of benefit to the protocol

–

---

<div class="post-metadata">

**Author:** ![Ceazor](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/ceazor/32/377_2.png) [@Ceazor](https://forum.summer.fi/u/Ceazor)\
**Post date:** [February 5, 2026, 7:51pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/17 "2026-02-05T19:51:24Z")

</div>

doesnt 6/8 slow reaction down here drastically.

if they can only init pausing. set caps to 0, (wish it could pulling funds from farms) type things. they it should be 2/8 at most.

---

<div class="post-metadata">

**Author:** ![Sixty](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/sixty/32/115_2.png) [@Sixty](https://forum.summer.fi/u/Sixty)\
**Post date:** [February 6, 2026, 1:26pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/18 "2026-02-06T13:26:01Z")

</div>

I agree with you here that 6/8 might slow down the reaction time. Which is why I suggested the liveness check; if it takes particularly long for the minimum amount of signers to react, reducing the signing threshold can be explored.

As it stands, though, the number of signers and the threshold are around the industry-accepted standard for best security practices when it comes to sensitive protocol operations.

---

<div class="post-metadata">

**Author:** ![Ceazor](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/ceazor/32/377_2.png) [@Ceazor](https://forum.summer.fi/u/Ceazor)\
**Post date:** [February 6, 2026, 8:31pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/19 "2026-02-06T20:31:17Z")

</div>

these are not really protocol operations. These are panic safety features\>

to add a new vault  
to change perFee  
to add new strat …etc

these need 6/8

But to panic.. it should be 1/8 IMHO.

it would be good if it was public, meaning anyone could trigger it, if there was someway to avoid competition sabatoge and vandalism. like some sort of meaningful bond

---

<div class="post-metadata">

**Author:** ![chrisb](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/chrisb/32/28_2.png) [@chrisb](https://forum.summer.fi/u/chrisb)\
**Post date:** [February 9, 2026, 12:31pm UTC](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675/20 "2026-02-09T12:31:54Z")

</div>

I also agree that 6/8 is quite aggresive and agree it’s not really at the same level as the L2 security councils, which I think this is based on.

I also believe that it should be \>1 though, as one person should not be able to trigger this without confirmation from another.

Perhaps 3 is ok, especially with the liveness check.

[Next page](https://forum.summer.fi/t/sip0-2-establish-guardian-module-emergency-risk-controls/675.md?page=2)