Status: Request for Comment
Visibility: @Recognized_Delegates @chrisb @halaprix @0xtucks @rspa_StableLab
Summary
This RFC proposes two updates to Lazy Summer DAO’s governance process:
- Reduce Voting Period from 5 days → 3 days
- Reduce Execution Delay from 2 days → 1 day for all networks
These changes aim to improve governance responsiveness without compromising participation or security.
What’s Changing?
| Parameter | Current Value | Proposed Value |
|---|---|---|
| Voting Period | 5 Days | 3 Days |
| Execution Delay (Base Networks) | 2 Days | 1 Day |
| Execution Delay (Other Networks) | 2 Days | 2 Days |
Note: The governance flow distinguishes between 1-day (Base network) and 2-day (other networks) execution delays.
Motivation
Lazy Summer’s governance has matured, with strong participation from active delegates and clear proposal standards. Reducing friction in the process will:
- Enable faster execution of vault launches, strategy changes, and reward adjustments
- Reduce “dead time” between DAO consensus and protocol action
- Align Lazy Summer with faster-moving governance systems in other high-performance DAOs
- Maintain a secure and reviewable window (1 or 2 days) for on-chain execution safety checks
A 3-day voting window strikes the right balance between participation and agility (majority of the votes are casted within the first 3 days of the vote publishing), and a 1 day delay provides a sufficient buffer for review before execution on Base Network.
New Governance Flow
Next Steps
- Collect feedback on this RFC over the next 3 days
- If there is broad support, a SIP4.X will be created and posted for vote on Tally
- Subject to quorum and successful vote, the new parameters will be implemented
Let’s make governance more efficient.
–jensei
