0. Clarification Initially proposed by Curia, this onchain proposal aims to transfer the requested funds ($4620 in SUMR) to a Safe Multisig address; as well as $420 in SUMR to CuriaLab.
Pricing of SUMR token used was VVWAP of March daily prices (excluding first and last 5 days).
This proposal introduces Delegate Rewards V2, a redesigned incentive framework for Lazy Summer DAO’s Reward Framework Qualified Delegate (RFQD) program. Recognizing that the current framework (SIP5.6) has demonstrated a structural misalignment between treasury spend and governance workload, this proposal replaces it with a Dual-Pool system anchored to a fixed maximum quarterly budget of $4,200 USD ($1,400 USD monthly). To protect quorum stability and elevate contribution quality, the monthly budget features an 85% baseline allocation ($1,200) strictly rewarding delegates who maintain at least an 80% onchain voting participation rate, alongside a 15% allocation ($200) reserved exclusively for the top 3 delegates driving high-value forum discussions as measured by the Peer Recognition Score (PRS). Finally, to align delegate incentives with the long-term economic health of the protocol, mitigate sell pressure, and reduce administrative strain, all funds will be managed by a dedicated Quarterly-Funded Safe Multisig and distributed following a monthly governance approval vote (tracked under future SIP3.Y.Z proposals).
The delegate compensation system formalized in SIP5.6 served Lazy Summer DAO well during its early governance phase. As the protocol’s complexity has grown—with DAO-managed vaults, expanded risk frameworks, and increasing governance throughput—the structural weaknesses of a static retainer model have become measurable and well-documented. 2.1 The Data Case for Reform
While forum discussions initially suggested a $1,500/month payout for high-value contributors, the DAO agreed this must serve as a long-term “north star.” Implementing that model today would require ~$25,000/month, which creates an unsustainable sell-side pressure given our lean stablecoin runway. Consequently, all V2 framework decisions have been heavily optimized to fit within our current fiscal constraints.To directly address the issues outlined above, Delegate Rewards V2 was designed with three primary objectives:
| Goal | How this framework addresses it |
|---|---|
| Quorum Stability | Pool A heavily weighted to make voting participation financially attractive |
| Contribution Quality | Pool B rewards top PRS scorers; pre-vote forum engagement > post-vote |
| Treasury Sustainability | Fixed quarterly budget cap; structured monthly payouts; quarterly reporting |
To execute the goals outlined above, the V2 Delegate Reward Framework will operate under the following parameters: 4.1 The Quarterly Budget Cap All delegate rewards will be drawn from a fixed quarterly SUMR budget, denominated in USD to provide predictability and recalculated at the start of each month. The budget for this framework is capped at $4,200 USD equivalent per quarter (distributed as $1,400 USD per month). 4.2 The Pricing Mechanism & Buffer To protect both delegates and the treasury from SUMR price volatility, payouts are calculated at the start of each month using a 20-Day TWAP, trimming the first and last 5 days of the month to minimize volatility and manipulation. A conditional 10% buffer, funded from multi-sig operations costs outside the $1,400 budget, is added to cover potential price drops between the calculation date and the actual payout execution. If the token price holds steady, delegates receive a small bonus; if it drops by up to 10%, their baseline USD compensation remains fully protected. Example: A 20-day TWAP of $0.20 converts the $1,400 budget to 7,000 SUMR; with the 10% buffer, the total payout becomes 7,700 SUMR. 4.3 The Dual-Pool Split The $1,400 monthly budget is divided into two distinct pools. This 85/15 split deliberately prioritizes quorum stability under a lean budget, while ensuring the contribution pool remains concentrated enough to be financially meaningful.
5.1 Monthly Qualification Audit: At the end of each month, eligibility is assessed. Jensei will track and confirm onchain voting participation rates (supported by Labs), while Curia will finalize and report the off-chain PRS leaderboard. 5.2 Quarterly KPI Report: Curia will publish a quarterly report covering:
| Phase | Dates | Milestone / Action |
|---|---|---|
| Week 0 | Feb 5 | Forum thread discussions initiated; delegates provided data exposing current model flaws, which were explored further in community calls. |
| Week 1 | Feb 9–13 | Core Delegate Incentive Working Group (DIWG) formed; hosted Workshop Part 1 to explore tensions and options. |
| Week 2 | Feb 16–20 | Hosted Workshop Part 2; secured foundational consensus on the budget cap, baseline voting, and Dual-Pool structure. |
| Week 3 | Feb 23–27 | Published the Transparency Hub and updated the Miro board to track framework designs. |
| Week 4-5 | Mar 2–13 | Drafted the V1 SIP skeleton and published to the forum as an open RFC to gather delegate feedback. |
| Week 6-7 | Mar 16–27 |
To avoid the inertia problem of V1, where a broken system persists despite the data, this framework includes a strict quarterly checkpoint. The DIWG will automatically trigger a formal framework review (and potential sunset) if either of the following thresholds are breached in the Quarterly KPI Report:
8.1 PRS and Data Provider Compensation Curia will serve as the dedicated Data Provider for the V2 framework. Responsibilities include maintaining the PRS data pipeline, dashboard, and publishing the quarterly report. For managing this operational and technical overhead, Curia will receive a lean retainer of $420 USD per quarter (representing exactly 10% of the total quarterly delegate payout budget, ensuring administrative costs remain strictly capped). 8.2 Technical Execution & Distribution Costs A lean budget for gas and signer stipends for the Safe Multisig will be introduced prior to the formal onchain vote.
If this SIP passes successfully, it will authorize the following immediate onchain actions to initiate the V2 Framework:
0x746bb7befd31d9052bb8eba7d5dd74c9acf54c6d0x17296956b4E07Ff8931E4ff4eA06709FaB70b8790xc2971FE806CE4438dA09e21fC7be7FB121Cf7e130x6860036343886107dF9995Bd57e8945be8Cb69b70x8795C17d02AF912C3586D03228e0165e9fdDE5260x17296956b4E07Ff8931E4ff4eA06709FaB70b879) for Data and KPI reporting.This is the finalized SIP draft based on the RFC consensus. Delegates and community members are invited to:
Target
Value
0 ETH
spender :
amount :
Target
Value
0 ETH
from :
to :
amount :
Target
Value
0 ETH
from :
to :
amount :
| Extended DIWG review to integrate delegate feedback and lock in final execution mechanics (Multisig, TWAP, Sunset Clause). |
| Week 8 | Mar 30–Apr 3 | (Current Phase) Finalized SIP 5.23 published to the forum for final community review. |
| Week 9 | Apr 6–10 | Active voting week. |
| Launch | Mid-April | Official implementation for Q2. |