[RFC] Arbitrum USDC Vault (OLD) User Reimbursement

I want to be very clear and transparent here. I have been extremely patient, constructive, and respectful throughout this entire process. I deliberately chose dialogue over escalation.

More than that:
I actually continued to support the protocol financially after the incident by redeploying meaningful amounts into new SUMR vaults, despite having lost 100% of my USDC in the Arbitrum Lower-Risk vault.
I’m happy to provide wallet addresses to the DAO to prove this if needed.

In parallel, I have actively worked to cool down discussions in the private affected-lenders groups, discouraging public noise, PR pressure, or more confrontational approaches — precisely because I believed the DAO was acting in good faith and moving toward a solution.

However, if the current strategy is to wait, delay, or assume that victims will eventually lose momentum, then I need to be honest: that would be a serious miscalculation.

If affected users start to feel that time is being used as a tool to exhaust them rather than to resolve the issue, the tone and the form of the mobilization will change — and I will no longer argue for restraint.

If the DAO has the will to propose a concrete path forward, it needs to do so now, not “later when conditions improve”, not after months of silence, and not contingent on market dynamics that are outside users’ control.

Trust is not restored by postponement.
It is restored by clear commitments, timelines, and accountability.

I genuinely hope we choose the former.

5 Likes

Thanks everyone for continuing to engage here; I hear the frustration clearly, and I want to respond constructively to a few recurring points, especially around “acknowledge the debt and pay it over time”.

I want to be very explicit:

  1. I am NOT going to argue that users expected “risk-free” outcomes, nor that this vault failure should be ignored.
  2. I DO disagree with the framing that curated vaults imply a standing guarantee of reimbursement regardless of cause or feasibility.

Risk management ≠ risk-free

Every DeFi user pays fees everywhere (Maker, Aave, Euler, Silo, Yearn, Balancer) and there is very little precedent where users were reimbursed when losses stemmed from external integrations and cascading failures, rather than a direct exploit or insolvency of the protocol itself (also rare).

This incident was:

  • a third-party stable failure (USDX),
  • combined with oracle design limits at Silo,
  • not a direct Lazy Summer Protocol exploit.

That distinction matters when we talk about precedent and long-term protocol design.


Several comments suggest allocating a small % of protocol revenue to reimburse users over time. This sounds reasonable, until we look at actual numbers.

Current protocol metrics (approx):

  • Annualized revenue: $419,660
  • Current TVL: ~$63.4M
  • Loss to cover (84% baseline): ~$1.26M
  • Allocation scenarios: 1–3% of protocol revenue

Scenario A: Current TVL (~$63M)

Annual revenue: $419,660

  • 1% allocation: ~$4,200 / year → ~300 years to reach $1.26M
  • 2% allocation: ~$8,400 / year → ~150 years
  • 3% allocation: ~$12,600 / year → ~100 years

At current scale, this is clearly non-viable.

Scenario B: $120M TVL

TVL ~1.9× current
Annual revenue ≈ $794,000

  • 1%: ~$7,940 / year → ~160 years
  • 2%: ~$15,880 / year → ~80 years
  • 3%: ~$23,820 / year → ~53 years

Still multiple decades, even at ~2× TVL.

Scenario C: $240M TVL

TVL ~3.8× current
Annual revenue ≈ $1.59M

  • 1%: ~$15,900 / year → ~79 years
  • 2%: ~$31,800 / year → ~40 years
  • 3%: ~$47,700 / year → ~26 years

Strong growth, still measured in generations.

Scenario D: $480M TVL

TVL ~7.6× current
Annual revenue ≈ $3.18M

  • 1%: ~$31,800 / year → ~40 years
  • 2%: ~$63,600 / year → ~20 years
  • 3%: ~$95,400 / year → ~13 years

Now we’re talking decades, but only after ~8× TVL growth.

Scenario E: $940M TVL

TVL ~15× current
Annual revenue ≈ $6.22M

  • 1%: ~$62,200 / year → ~20 years
  • 2%: ~$124,400 / year → ~10 years
  • 3%: ~$186,600 / year → ~6–7 years

This is the first scenario where a revenue-based recovery becomes plausible within a human timeframe, and it requires ~$1B TVL, sustained.

Even under optimistic growth assumptions, “programmatic reimbursement via fees” is measured in decades, not months or even a few years and this is why I keep pushing back on the idea that there is an “obvious middle path” being ignored. The middle path collapses under basic math.

So when people say “just stream it over time”, what the math actually says is:

Streaming only works if the protocol becomes much larger first.

That doesn’t mean “never”.
But it does mean “not now, and not without explicit growth conditions.”

It is important to clarify and highlight here that I was not assuming SUMR Token and its potential price increase in these TVL growth assumptions - but very briefly:

SUMR Price (USD) SUMR Needed % of DAO Treasury (~123.43M SUMR)
0.005598 224,200,143 182% → impossible
0.01017 123,425,821 100% → just feasible
0.03 41,849,667 34% → feasible
0.09 13,949,889 11% → very feasible
0.15 8,369,933 6.8% → minimal impact

Here it becomes quite clear that the potential for any reimbursement could be made only paired with the protocol growth and treasury SUMR value growing.


On acknowledgment vs. false certainty

I fully agree with one thing some of you said: “Postponement without structure feels like abandonment.”

Where I disagree is that committing to an unpayable obligation today restores trust. In my view, that replaces one failure with another, promising something the DAO cannot realistically deliver.

A credible approach must imo:

  • be conditional,
  • be explicitly feasibility-gated,
  • and not rely on revenue streams that mathematically cannot close the gap.

What a realistic framework could look like

If this discussion continues (and I believe it should), the only paths I see that don’t mislead anyone are trigger-based, not schedule-based.

For example (illustrative, not prescriptive):

Level 1:
SUMR price sustains > X
Liquidity > Y
Treasury stable holdings > Z
→ partial reimbursement unlock

Level 2:
Treasury reaches N% of loss amount in non-SUMR assets
→ additional tranche

Level 3:
External recovery (e.g. Silo / USDX) materializes
→ debt receipts become withdrawable

Until conditions like these exist, any “timeline” is unfortunately symbolic rather than executable.

On Silo responsibility (not deflection)

Pointing to Silo is not about shifting blame, it’s about where the debt actually lives.

Silo holds the debt. The DAO holds the receipts, and is actively scanning for any liquidity/backing restored.

If those positions are ever restored, that is the cleanest and least destructive recovery path for users. Pretending otherwise does not help affected lenders; it just concentrates risk onto a DAO that did NOT custody those funds.


I understand why hope is fading, that’s on all of us to acknowledge.
But I don’t believe honesty about constraints is abandonment, nor do I believe that promising repayment paths that require 15–300 years restores trust.

I remain open; genuinely; to non-destructive mechanisms that close this gap within a realistic horizon. If someone has numbers that show otherwise, I’m very willing to review them.

What I don’t want is for this DAO to replace a painful loss with a second failure: committing to something that cannot be honored.

I appreciate everyone who continues to engage, even when emotions are understandably high.

1 Like

@jensei

I’ll keep this short and focused.

The problem here is no longer feasibility — it is the persistent refusal to acknowledge responsibility.

This was not a generic DeFi accident. Two concrete, governance-level failures made this outcome possible:

  1. Allowing a “Lower Risk” curated vault to gain exposure to a market relying on a hard-coded $1 oracle for an experimental stablecoin.
    That is a fundamental risk-management error, not hindsight.
  2. Having no mechanism to pause withdrawals or enforce loss socialization, which turned a ~16% exposure into 100% losses for last-out depositors.

Without these two failures, we would not be here.

Debating treasury math while avoiding ownership of those decisions is the core issue.
Reimbursement discussions cannot be meaningful if responsibility itself remains unacknowledged.

Until that changes, postponement will feel less like prudence — and more like avoidance.

7 Likes

Proposal: Recovery Receipts & Revenue-Routed Recovery Peg

  • Using a snapshot of affected addresses, issue Recovery Receipts equal to each user’s unrecovered USDC claim (1 receipt = 1 USDC of claim).
  • Route a fixed share of protocol revenue into an on-chain Recovery Pot.
  • Define a live recovery peg:
    • peg = RecoveryPot / TotalOutstandingClaims
  • At any time, users can redeem receipts at the current peg (e.g., if the peg is 10%, redeem 10% now). Redeemed receipts are burned.
  • Burning receipts permanently reduces outstanding claims, so future revenue services fewer claims, accelerating full recovery for those who stay (assuming revenue remains non-zero).
  • Any external or partial recovery of the underlying funds is routed into the Recovery Pot, increasing the peg for all outstanding receipts.
  • Optionally, whitelist or create a market for receipts to be sold rather than redeemed, applying a small trade fee that is routed to the Recovery Pot to further accelerate recovery.

This creates a structured recovery path without immediately depleting the treasury and gives users agency to exit at the current peg or stay for continued upside as coverage increases.

Also, why limit the recovery stream to 1–3% of protocol revenue? A much higher allocation seems necessary if the goal is to make real progress rather than stretch recovery indefinitely.

7 Likes

Just like that, discussion have died. Godspeed

2 Likes

hey @LizardLizardLizard good to see you on the forum! I have previously shared my thoughts on this proposal at the current status of discussion here:

At the moment, I do not see any realistic proposal opportunity here, so my best suggestion is to put this one on ice and track the status of the treasury (over some months). Again, this is my personal opinion; and its of essence for everyone to understand that pushing this (onto SIP) or any bringing up any other proposal (RFC → SIP) here on forum or onchain is permissionless - and anyone is free to do so.

At the end of the day the onchain governance decides via voting of @Recognized_Delegates and community members holding stSUMR.

2 Likes

@jensei I understand that governance is permissionless and that anyone can submit an RFC.

But there is a difference between what is technically possible and what is institutionally responsible.

As an affected depositor, I do not believe it is the victims’ role to design the reimbursement framework for a failure that occurred inside a curated, fee-generating product.

Users deposited into a vault marketed as “Lower Risk / set-and-forget,” curated and surfaced by Lazy Summer. When a systemic failure occurs within that structure, it is reasonable to expect that the protocol’s leadership and core contributors take the initiative in proposing a structured path forward.

Permissionless governance does not remove the protocol’s responsibility to lead.

History also matters here. Major DeFi protocols that faced crises — whether exploit-related, oracle-related, or integration-related — did not simply say “anyone can propose something.” They stepped up with concrete frameworks, structured recovery paths, and clear next steps. That is how trust is rebuilt.

If the message becomes “if someone wants to propose something, feel free,” it implicitly shifts the burden from the protocol to the victims. That is not a healthy precedent for a curated yield platform.

What many of us are looking for is not an open-ended forum thread — but a concrete trajectory, proposed by the protocol itself, that acknowledges responsibility and defines next steps.

Without that, the signal to current and future depositors is deeply concerning.

9 Likes

Updates? This has been quite a traumatic experience for myself and others, and the way this has been handled, has only made it worse.

6 Likes

Summerfi´s support has also been terrible. Saying they will resolve it and automatically refund. It´s been 124 days without solution.

3 Likes

So as far as I understand summer DAO doesn’t have liquidity to cover anything.
What are the other options?
What is being done?
Other responsible parties like Silo or Block Analitica??
Anyone reached out to them, should we reach out to them?
What was the management fee for, why Block analitica isn’t taking any responsibility it was their job that everyone should suffer only 16% loss I guess?
Anyway, my hopes are pretty low.
I do think that some people in their team do understand that it’s significant amount of money lost and greatly affects mental wellbeing.
I sure hope that nothing like that ever happens to anyone.

6 Likes

Is the Resolve exploit which just occured (see https://x.com/ResolvLabs/status/2035601833645768943?s=20) impacting the recovery of SummerFi’s part in any way?

Summerfi is an absolute joke. If a “low risk” vault collapses in 2 months, than how fast does a medium or high risk vault collapse?

3 Likes

Updates? They are just going to act like nothing happened?

2 Likes

as answered previously here:

I am not aware of any recovery of assets. As the Lazy Summer DAO treasury (imho) cannot cover for any meaningful reimbursement I have not proceeded with promoting this RFC to an SIP stage.

I am (as always) curious about thoughts of other @Recognized_Delegates - but without any specific (realistic, and meaningful) solution I would suggest to close this RFC/topic until any new updates would become apparent.

Closing this topic would amount to trying to sweep this protocol failure under the rug.

6 Likes

Is there a long term plan? Is there an insurance fund, how much does it have, and are funds being distributed to it?

Is it possible the project can cease, and all the assets can be liquidated to pay back the victims?

3 Likes

Hey guys, the entire Lazy Summer treasury can be viewed transparently onchain, and as stated above, there is still not enough, unfortunately, to realistically reimburse affected users. I don’t think the intention is to sweep this discussion under the rug, but rather to wait for more favorable conditions for a reimbursement.

3 Likes

You can’t just close it and let it slip as if nothing happened. You have to take responsibility and propose a solution to this.

I’m really tired of the lack of responsibility from the team and BlockAnalitica, it’s unthinkable after what happened.

I’m not going to go into all the details again, they’ve already been listed many times and honestly shouldn’t even be needed because it’s as simple as this:

YOUR system failed to socialize the loss, yet WE are the ones paying the 100% loss.

You need to take action and propose a solution.

5 Likes

Absolutely agree. It´s been shoved under the carpet like nothing happened. Customer service is not responding anymore. Summerfi tokens are useless.

Drarox, maybe if we get enough people together we can put in a legal claim. Let me send you a direct message. Summerfi takes 0 responsibility and 0 action for selling a product under “low risk” where we lost all our funds with a month.

4 Likes

Meaning waiting for the next bull market? I think most people effected are fine with that, but communication is missing. Without communication it is actually putting it under the rug, hoping people stop claiming.

1 Like