Thanks to everyone who joined Community Call #10. While the previous calls focused on product structure (DAO-managed vaults, risk caps, liquidity strategy), this session was intentionally operational.
This was less about new surface area, and more about strengthening foundations. We tackled questions like:
- How governance executes in practice?
- How we respond under stress?
- How we incentivize real work inside the DAO?
Announcement: Community Call #10: Governance, Security & Delegate Rewards
Recording: https://youtu.be/xGxMcpVxp58
Context & Purpose of the Call:
As Lazy Summer scales, governance load increases. More vaults, more proposals, more capital → more responsibility.
This call centered around three operational questions:
- Is our governance cadence healthy and sustainable?
- Is our security posture strong enough for scale?
- Are delegate incentives aligned with real contribution and treasury constraints?
Governance Cadence & Active SIPs
We opened with a brief walkthrough of live proposals on Tally.
[SIP5.7] January Referral Payouts
- 59,000 SUMR & ~1.86K USDC distributed
- 666 recipients
- Fully predefined Merkle distribution
- No contract changes
- Routine execution
[SIP3.13.1] Governance V2 Locker Rewards (January USDC)
Important milestone:
- First full month of Governance V2 revenue sharing
- 20% of protocol revenue distributed to locked SUMR
- Paid in yield-bearing LVUSDC (auto-deposited into the Base USDC Lower Risk Vault)
- Distributed via Merkle upon execution of the proposal
Technical note from @chrisb:
“Bridging transactions may temporarily cause simulation failures. Re-simulation will occur once bridging finalizes.”
[SIP0.2] Guardian Module
This proposal establishes a narrowly scoped, time-bound emergency Guardian module.
Key principles:
- Emergency-only powers
- 180-day maximum duration
- Fully accountable and transparent
- No expansion of authority beyond defined scope
Discussion highlighted the importance of:
- Liveness checks
- Accountability mechanisms
- Clear operational boundaries
Aerodrome Meta-Governance Update
@Sixty provided an update on veAERO accumulation and voting strategy.
Current Status:
- ~114,000 veAERO across 5 NFTs
- Acquired at ~9.72% average discount
- Additional AERO and ETH remaining for future swaps
- Voting already active toward the SUMR-USDC pool
AERO rewards from protocol-owned liquidity (via Arcadia) are now being forwarded directly into meta-governance instead of sitting idle in treasury.
SEAL Safe Harbor & Incident Response
This was one of the most important discussions of the call. @dickson (SEAL 911) joined to walk through the Safe Harbor framework.
What Safe Harbor Does
- Authorizes vetted whitehats to intervene during active exploits
- Requires full fund return
- Establishes predefined bounty terms
- Provides legal clarity so whitehats can act immediately
This framework already exists across major protocols (Uniswap, Balancer, zkSync, etc.).
Key clarifications:
- Safe Harbor only applies during active exploits.
- It does not override normal bug bounty processes.
- It is a unilateral agreement with the broader whitehat ecosystem; not just SEAL.
- Identity disclosure requirements are configurable (anonymous, pseudonymous, KYC).
We also discussed operational coordination:
- Incident rooms
- Guardian interaction
- Fund return flows
- Asset scope definitions
Next Step:
Finalize asset scope + bounty parameters in RFC → move to SIP.
Delegate Rewards
This was the core working discussion where @Curia presented analysis of 2025 delegate rewards and identified structural misalignment:
- Quiet months were overpaid
- Busy months were underpaid
- Compensation did not scale with governance workload
- Fixed retainers grow treasury burden as delegate count increases
Treasury reality:
- ~94% of treasury value in SUMR
- ~6% in stable/liquid assets
- Sustainable monthly payout currently limited
Proposed Direction
Two structural adjustments:
- Dynamic Base Pay
- Scale retainer with governance activity levels
- Protect treasury during low activity months
- Peer Recognition Score (PRS)
- Shift from pure quantitative metrics (attendance/comments)
- Toward contribution validation by peers
- 6-month pilot with no compensation impact initially
Additional Discussion Points
- Should compensation tiers vary by proposal importance?
- Should some proposals carry higher weight?
- Should rewards vest or be locked in SUMR to reduce sell pressure?
- Should quorum mechanics be revisited?
- How do we ensure incentives drive signal quality — not noise?
Notably:
“Lazy Summer does not struggle to reach quorum under Governance V2. This suggests incentives should optimize for quality, not turnout.”
Governance V2 Quorum Clarification
Under Governance V2:
- Quorum is based on staked SUMR supply
- Only staked SUMR can vote or delegate
- Percentage is adjustable (contractually limited)
Communication improvement identified: Many holders may not realize unstaked SUMR has no governance power. Education matters.
Emerging Consensus
Across security, incentives, and meta-governance, the same structural question surfaced:
Can we scale governance without diluting standards? This call was about discipline.
- Codifying emergency response
- Tightening incentive design
- Aligning treasury reality with contributor expectations
- Making governance sustainable before it becomes fragile
Action Items
- Engage in SEAL Safe Harbor RFC
- Participate in Delegate Incentive exploration and future Working Group co-created by @Curia
- Vote on active SIPs
- Continue forum discussion
Closing Thoughts:
Bear markets are not setbacks. They are build markets and governance quality compounds quietly.
Thanks to everyone who joined, contributed, and continues to engage thoughtfully. See you on the next call.
–jensei