1. Overview:
This proposal continues the delegate compensation program first approved in [SIP5.6], this time applying it to June 2026. The goal is to sustain high-quality governance engagement and reward meaningful participation from active delegates across Lazy Summer Protocol governance.
Extending [SIP3.11.8] (May Distribution) to [SIP3.11.9] (June Distribution).
Starting from April 2026, the Lazy Summer DAO has approved of Delegate Rewards Framework V2 via https://forum.summer.fi/t/sip5-23-delegate-rewards-framework-v2/793 - with the month of June following the newly setup guidelines for rewards distribution.
Due to lack of funds in the Delegate Rewards Framework V2 Multisig, this proposal includes a transfer of SUMR to the multisig for further distribution.
This proposal includes the 6th distribution of rewards to Aerodrome Metagovernance signers.
2. Motivation:
Active and accountable delegates remain a cornerstone of protocol governance. June 2026 focused on SUMR staking, delegate, and referral rewards distribution, offboarding low usage vaults, extending SUMR staking rewards and adjusting governance parameters. Compensating delegates for their time and contributions ensures continued accountability and engagement.
3. Specification:
| Item | Value |
|---|
| Rewards Token | SUMR |
| Delegate Rewards | 569,513.91 SUMR |
| Source of Delegate Rewards | Delegate Rewards Multisig (Base) |
| Aerodrome Signer Rewards | 237,297.46 SUMR + 500 USDC |
| Source of Aerodrome Signer Rewards | Lazy Summer DAO Treasury (Base) |
| Total Distribution Amount | 806,811.37 SUMR & 500 USDC |
| Distribution Schedule | One-time disbursement following onchain approval |
| Eligibility Period | June 1st – June 30th (2026) |
| Distribution Method | Direct transfer to verified delegate wallet addresses |
3.1.1 Stipend Calculation Methodology
- Daily Prices & Volumes Used
| Date | Volume (USD) | Close Price (USD) |
|---|
| Jun 06 | 1,148.45 | 0.00191102 |
| Jun 07 | 47.16 | 0.00189860 |
| Jun 08 | 26.81 | 0.00191068 |
| Jun 09 | 17.61 | 0.00191043 |
| Jun 10 | 219.06 | 0.00190472 |
| Jun 11 | 49.56 | 0.00189607 |
| Jun 12 | 16,008.47 | 0.00210095 |
| Jun 13 | 1,098.87 | 0.00210569 |
| Jun 14 | 2,470.12 | 0.00211644 |
| Jun 15 | 169.57 | 0.00211632 |
| Jun 16 | 2,529.93 | 0.00211879 |
| Jun 17 | 235.67 | 0.00212140 |
| Jun 18 | 4,227.47 | 0.00212879 |
| Jun 19 | 638.05 | 0.00211363 |
| Jun 20 | 7.59 | 0.00212891 |
| Jun 21 | 6,532.44 | 0.00210794 |
| Jun 22 | 23,980.00 | 0.00211741 |
| Jun 23 | 7,827.42 | 0.00207957 |
| Jun 24 | 1,363.48 | 0.00204014 |
| Jun 25 | 3,156.36 | 0.00210469 |
| Jun 26 | 87.81 | 0.00209107 |
Source dataset: CoinGecko historical export.
- Volume-Weighted Average Trading Price (VWAP)
For VWAP we need price×volume. We will exclude first and last 5 days of the month from the VWAP weighting* (meaning VWAP is for June 05-26).
VWAP (June 05–26) ≈ $0.002107
- Convert $250 to SUMR
- 250/0.002107 ≈ 118,652.11 SUMR
- Transfer 250 USDC to each signer to lift up the strain on SUMR in the DAO Treasury (Total 500 USDC).
4. Risk Assessment:
- Onchain vote will authorize SUMR disbursement from the DAO Treasury to Delegate Rewards Multisig and Aerodrome Signers.
- Delegate rewards according to the framework V2 will be disbursed from the Delegate Rewards Multisig established for this purpose.
- Delegate participation data was sourced from the Lazy Summer Governance Dashboard.
- The final delegate list and breakdown is made publicly available here.
- The final delegate PRS Score analysis was delivered by @Curia and can be found here
- Any entity may only receive compensation through a single verified delegate address.
- Suspected Sybil delegates will be excluded, subject to verification by @Recognized_Delegates and @Curia.
5. Voting:
If YES - Approve a transfer of 132,064.80 SUMR from treasury to the Delegate Rewards Multisig. Approve a transfer of 237,297.46 SUMR + 500 USDC disbursement to Aerodrome Metagovernance June signers. Delegate Rewards 569,513.91 SUMR will be distributed via multisig.
If NO - Do not compensate for June; continue with further discussion.
Tagging @Recognized_Delegates for a check up as always.
--jensei
