[RECAP] SUMR Transferability Community Call #3

[jensei]

Thanks to everyone who joined our third SUMR Transferability Community Call!
This session focused on final readiness for SUMR transferability, the rollout of Governance V2 + the new Staking & Lock Module (Staking V2), and a walkthrough of the new staking UI where we for the first time had a sneak peak into how users will migrate, stake, lock, and start earning dual rewards (SUMR + USDC from protocol revenue).

Below is a full recap of the call

---

Context & Where We Are

We’re still on track for SUMR transferability, but with one small update to process.

• The Sherlock audit contest for Governance V2 & the Lock Module is nearly finished; no critical issues, final parameter reviews in progress.
• To avoid delaying deployment by another week, contributors proposed a combined governance vote that will:
  • Add the Lazy Summer Foundation multisig as a temporary governor (to perform whitelisting)
  • Allow the Foundation to whitelist the staking contracts immediately upon deployment, without waiting for a second vote.

[SIP]: [SIP5.13] Multi-chain Foundation Roles Setup
[TALLY]: Lazy Summer DAO (Official) | SIP5.13: Multi-Chain Foundation Roles Setup

Target for SUMR transferability remains: ~November 18 (pending DAO approval) with initial transferability launching on Base, with expansions to mainnet and other chains later.

As shared during the call:

“We are living up to the same timeline; governance stays in control, and we avoid unnecessary slippage.”

---

Staking V2 & How Locking & Rewards Will Work

On this call @samehueasyou demoed the new Staking & Lock module UI, where SUMR becomes productive governance.

Dual Rewards for Lockers:

1. SUMR emissions (~5,000/day — proposal live on forum)
2. USDC from protocol revenue (20% of protocol yield), distributed as LV (vault) tokens, which continue compounding automatically!

WIP for the Staking UI:

Locking Mechanics:

1. Choose lock duration → receive a multiplier on voting power + yield
2. Range: no lock (1x) → 3 years (~7.26x)
3. Locks are non-extendable → plan ahead or use multiple lock positions (e.g. 3-year + 6-month split)

WIP for the Locking UI:

WIP for the All Locked SUMR UI:

Capacity Limits (NEW):
Each lock duration has a maximum SUMR capacity.

1. If a lock “bucket” is full → UI shows it as unavailable.
2. Users can choose a shorter duration or lower the amount.
3. Governance can vote to increase caps in the future.

As shared during the call:

“It’s conviction-weighted staking but with built-in scarcity.”

---

Rewards, Yield Loops & Transparency

The UI now helps users see how their lock contributes to long-term value.

Revenue → USDC to Lockers Flow:
More SUMR locked → stronger price → higher vault APY → higher TVL → more protocol revenue → more USDC rewards to lockers.

The UI shows:

1. Expected USDC earnings.
2. % of total SUMR supply locked.
3. Average lock duration to gauge community conviction.
4. Real-time available capacity per lock term.

This should add both transparency and social proof to governance participation.

---

Migration to Governance V2

Migration is manual (opt-in) as no one is forced. Users will be able to migrate on their own, directly via the new UI.

Migrating to V2 gives access to:

1. SUMR daily emissions
2. 20% USDC revenue sharing (as LV tokens)
3. Full voting + delegation in the new governance system (xSUMR / sSUMR; naming to be finalized on forum)

Important:

• You cannot extend a lock duration after creating it
• Early withdrawals are possible anytime, but with a penalty (up to 20%, linearly decreasing over time), depending on the lock period.

---

Liquidity & Launch Strategy

1. The Lazy Summer DAO treasury will bootstrap initial liquidity, likely SUMR paired with stable assets on Aerodrome (Base).
2. Community LPs will be encouraged to join, expected to be incentivized with SUMR rewards & USDC via governance proposal.
3. Full liquidity parameters (fees, gauges, emissions) will be posted to the forum before deployment.
4. Transferability won’t be a “free-for-all”, it will be intentional, aligned with incentives and clear onboarding education.

---

How to Prepare

For existing SUMR holders:

1. Decide your lock strategy, multiple durations if needed.
2. Review Governance V2 migration process.
3. Confirm your delegate, or plan to vote yourself.
4. Be ready for the whitelisting + transferability vote.

For new users or Base newcomers:

1. Bridge funds to Base.
2. Keep some ETH for gas.
3. Follow upcoming staking tutorials.

For LPs:

1. Watch for the Aerodrome liquidity proposal on the forum.
2. Review incentives and parameters before contributing.

---

Open Questions / Future Possibilities

Topic	Status
Bonus for early lockers?	Not planned, lock capacity limits already create scarcity.
Governance power for LV (vault) token holders?	Not supported at launch, potential future discussion post-Gov V2.
Name for locked SUMR (xSUMR vs sSUMR)?	To be decided via forum proposal.

---

Next Milestones

1. Publish staking & locking tutorials
2. Treasury plan for Aerodrome liquidity
3. Governance vote to enable transferability

Expected SUMR transferability: around Nov 18th

---

Closing Thought

Every week brings us closer, so if you haven’t joined this time, keep an eye out for the next community call, soon.

Stay strong in these turbulent times, and get ready for the Summer to SUMR transition, with us!

[Eren_DAOplomats]

Awesome recap, thanks for pulling all this together @jengajojo_daoplomats . I read through everything, and the new Staking V2 is looking like a huge win. I like the dual rewards idea. I did have one question about the Capacity Limits, which is a pretty unique idea. What’s the main game plan for setting those initial caps? Are we hoping to get a balanced mix of people across all the lock durations ?
Anyway, it’s cool to see this all coming together. Definitely gonna be at the next call!

[jensei]

Hey @Eren_DAOplomats, happy that you have enjoyed the recap! This is why I am writing them out, for those that did not manage to join in for the call - to have the possibility of catching up!

Regarding your question, imo the initial capacity limits are mainly there to help balance inflows and test demand across lock durations. The goal isn’t strict equal distribution but rather a healthy mix that gives us data to fine-tune future caps and reward weights once we see how users actually allocate.

Below I am re-posting some of @chrisb takes on the topic of lockups:

SUMR TR-WG Checklist

Thanks all for the comments, will try and address some of them, and some rationale for reasons why, and some changes as put forward by @halaprix while building out the contracts etc too… I disagree that it’s defensive. I think adding the real yield component in USD is what creates the demand here, it will be one of few tokens that you can actually earn from, that doesn’t just involve the same token that your locking. If it was just additional SUMR rewards, I agree that this would be fairly def…

---

@chrisb

The following buckets are proposed too, with caps;

Bucket	SUMR Caps	Can be changed by Gov after deploy
0 days (No lockup)	15,000,000	Yes
0 - 14 days	0	Yes
14 - 90 days	15,000,000	Yes
90 - 180 days	22,500,000	Yes
180 - 365 days	22,500,000	Yes
365 - 730 days	50,000,000	Yes
730 - 1,1095 days (max period)	1,000,000,000 (Total supply of SUMR)	Yes

This represents a total of 97.5m SUMR tokens that can be staked and locked for less than 2 years. There is no cap (why it’s the total supply) on the 2-3 year period.

Also, at the start, it has 0 day lockup cap - primarily for helping and ensuring users can deposit for the governance transition - but Governance, after launch, may want to change the cap to 0 for the 0 day lockup, forcing SUMR holders to stake for a minimum of 2 weeks at anytime. However, it is expected that the short cap would likely be filled very quickly though, so maybe have a small cap also creates some sort of forced lockup as people withdrawing from it may think it could be difficult to deposit back into it.

[tannus]

Hi everyone, and thanks for the detailed insights shared regarding SUMR transferability.

I’m currently modeling SUMR’s long-term revenue growth, and there’s one structural point I need clarification on:

Should institutional vaults (like MakerDAO’s 2.5B TVL in Summer Pro) be considered “private vaults” outside of the DAO revenue scope, or will they eventually be incorporated into the DAO in some form?

My assumption so far is that MakerDAO’s TVL does not generate protocol revenue that is distributed to SUMR holders, which dramatically reduces the current revenue base and changes the growth curve.

However, I’m not sure whether other institutional vaults (existing or coming) will be treated the same way — i.e., segregated from our DAO — or whether they could at some point feed into DAO revenue and thus into SUMR distribution.

This distinction is crucial for the revenue-share model and for understanding SUMR’s potential.

Could the team clarify how institutional vaults are categorized for revenue distribution purposes?

Thanks in advance!

[JoeSummerFi]

Hi,

Thanks for this question, it’s an important clarification.

Summer.fi Pro is indeed an independent product (and set of infrastructure). The Lazy Summer Protocol and the protocol/DAO does not monetise Summer Pro TVL. It’s also important to note that the institutional vaults you mention are not related to Summer.fi Pro in any way.

Within the Lazy Summer Protocol the monetisation of TVL is as shown on the monetisation charts of the public Dune dashboards here: https://dune.com/lazysummer/lazy-summer-protocol

e.g. this was 0.58% annualised blended average across all vaults as of 20/11/2025

Currently, for all DAO managed Vaults, the annualised fee rate on stable asset types is 1% and on volatile assets is 0.3%. The blended average fluctuates relative to stable/volatile proportions.

In addition to the DAO managed vaults, there will be deployments of institutional “self managed vaults” (the first of which was deployed this week - more announcements to follow on this soon). These are independent deployments outside of DAO control, with commercial terms negotiated with each institutional user on a case by case basis. These Vaults will still generate revenue for the DAO and we expect this to be somewhere around 20bps on vault TVL. Unlike DAO vaults, this revenue has no associated direct costs and could be seen as pure profit. We expect these vaults to be a significant source of future TVL and revenue growth.

At the launch of Staking V2, the revenue share mechanism assumes 20% of all revenue will be distributed via staking rewards. However, DAO vault revenues are currently associated with a gross margin of ~28% (after DAO related costs associated with operating the Vaults) whereas revenues from Self Managed Vaults are effectively a 100% gross margin. Given these different cost profiles, it’s expected that the DAO may vote to associate staking rewards to a share of earnings rather than top line revenue in due course.

Full details of the proposed revenue share mechanism can be found in this forum post

[RFC] Staking V2 Launch Parameters incl. Revenue Share

1. Summary: This RFC will be to outline the proposed initial parameters for the new SUMR Staking V2 Module, and then receive feedback from the community in order to align and go to vote on the dates outlined in this post: Staking V2 & Governance Upgrade, leading to SUMR Transferability - Proposed Timeline and Actions 2. Context & Motivation: Staking V2 represents one of the biggest upgrades to the Lazy Summer Protocol since it launched in February this year. And not just because it’s a precurs…

I hope this clarifies things

[jensei]

Thanks for the detailed breakdown, @JoeSummerFi! This really helps clarify the distinction between DAO-managed vaults, Summer.fi Pro, and the self-managed institutional vaults (which are indeed exciting). The nuance around gross margin differences is super useful, especially seeing that self-managed vaults can effectively contribute near‑pure profit while remaining independent.