Hey Lazy Summer community,
We at Block Analitica, acting as the risk curator for the Lazy Summer Protocol, want to bring more transparency around the Arbitrum USDC vault and to address the risk curation actions taken by BA during the period of the last couple of weeks.
Starting from late October, BA Labs has proposed refraining from onboarding assets identified mainly with significant recursive collateralization risk, as it can be seen here.
As this has led to limiting exposure to zero to assets including xUSD and deUSD, which have experienced a depeg in the following weeks leading to losses across numerous Euler, Silo, Morpho vaults, even some major lending venues like Compound v3 (deUSD), the losses were mitigated fully on Lazy Summer Protocol.
The same action was taken for the sUSDx Silo ARK on Arbitrum by setting the caps to zero on Nov-04-2025 09:56 AM UTC (tx), roughly 2 days before the USDX started depegging (Nov-06-2025 ~12:00 UTC). This prompted Lazy Summer Protocol keepers to initiate a continuous withdrawal process. However, following the Balancer v2 exploit, the StablesLabs team and its LPs withdrew all liquidity from the Arbitrum network (among others), resulting in 100% utilization.
According to the risk model set by Block Analitica, the classification of USDX as collateral identified it as an exotic* asset within this framework, thus ensuring limiting the exposure to it on the both Lazy Summer Protocol and vault level:
- At the time of setting caps of sUSDx Silo ark to zero, total Lazy Summer Protocol exposure to USDX was <0.9%.
- The exposure of the Arbitrum USDC vault (fleet %TVL) to sUSDX Silo ark at the time of USDX depeg was ~16%.
Namely, the loss socialization was feasible only via governance vote, while the vault deposit caps were set to zero (tx) soon after the depeg of USDX was identified.
*At the time of the sUSDx caps setting to zero, the Lazy Summer Protocol had potential exposure to over 250 different collateral assets. Our risk framework included a collateral classification system, setting parameters accordingly to balance the risk/reward ratio of several different ARKs.
Since then, BA Labs proposed full liquidity reallocation to ARKs with more conservative risk settings (Aave v3, Compound v3, Fluid, Sky sUSDS, Spark, and similar), mainly due to multiple tokens being subject to major withdrawals in the light of recent events. This remains the case as of this writing.
Any response to UI-related comments from the Lazy Summer community remains at the discretion of Summer.fi.
Below, we’ll share the risk-related information and risk management methodologies we use as the risk curators of Lazy Summer Protocol, with hope of clearing any doubts.
The “Lower Risk” label at the vault level does not indicate zero exposure to collateral assets with non-market pricing mechanisms within the ARKs onboarded to that vault. By way of example, several ARKs currently onboarded to “Lower Risk” vaults already rely on collateral with hardcoded or redemption-based pricing, such as Aave v3 with USDe, as well as (w)stETH/ETH rates across multiple major lending venues, which is still true today including USDC and ETH fleets with “Lower risk” UI labeling on Mainnet.
Furthermore, we note that beyond exposure to less conservative collateral assets as assessed by the BA under its risk framework, the main distinction in how the BA treats “Higher Risk” vaults from “Lower Risk” vaults lies in the application of more aggressive risk parameters (e.g., higher caps, higher maximum % of TVL to onboarded ARKs, etc.).
Please find more publicly available information on the BA’s approach to risk tranching within Lazy Summer Protocol here and here.
As far as potential recovery of the funds are concerned, apart from the announcement coming from the Silo team they’ve confirmed submitting an official registry of lenders impacted by the Stream and Stable Labs incidents - documenting all affected addresses and exposures as of Nov 7, 2025, and the check of Lazy Summer Protocol ARK address inclusion in the above, we (BA Labs) have no additional information as of now about the recovery process and are actively monitoring the developments of any potential funds recovery, including coordination with Silo and, where relevant, with Summer.fi and Lazy Summer teams.
Furthermore, we note that any decision regarding potential compensation for users affected by the sUSDx/USDC Silo market on Arbitrum falls exclusively under the remit of the Lazy Summer DAO and its governance process. At this time, we are aware that steps are already underway in the form of preparing a forum proposal to address this matter.