# What is the status of Silo Lender ARB/USDC.e

**URL:** <https://gov.yearn.fi/t/what-is-the-status-of-silo-lender-arb-usdc-e/14572>\
**Category:** Feedback\
**Created:** [12 December 2025 10:20 UTC](https://gov.yearn.fi/t/what-is-the-status-of-silo-lender-arb-usdc-e/14572 "2025-12-12T10:20:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![miohtama](https://dub1.discourse-cdn.com/flex013/user_avatar/gov.yearn.fi/miohtama/32/4990_2.png) [@miohtama](https://gov.yearn.fi/u/miohtama)\
**Post date:** [12 December 2025 10:20 UTC](https://gov.yearn.fi/t/what-is-the-status-of-silo-lender-arb-usdc-e/14572/1 "2025-12-12T10:20:37Z")

</div>

Hi,

At Trading Strategy, we manage independent data sourcing and vault dashboards. My question is about some of the Yearn vaults, for which I could not find details, and we need to make a decision whether to mark these vaults abandoned or stuck, and we are also trying to figure out if these vaults have been hit by the xUSD fallout.

Silo lender ARB/USDC.e has an excellent return today, but I am not sure if this is because it’s of Stream xUSD fallout exposure or if it is genuinely a good vault.

My question is, what is the status of this vault, and should it be included in the benchmarks?

> **[USDC-2 yVault](https://tradingstrategy.ai/trading-view/arbitrum/vaults/usdc-2-yvault)**
>
> Vault details for USDC-2 yVault vault on Yearn on Arbitrum One

> **[Yearn Vault](https://yearn.fi/v3/42161/0x9fa306b1f4a6a83fec98d8ebbabedff78c407f6b?tab=strategies)**
>
> The yield protocol for digital assets

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/yearn/original/2X/f/f2c2bc036e38762dc942bc8b8c323de2a9a9c0e8.jpeg)

---

<div class="post-metadata">

**Author:** ![miohtama](https://dub1.discourse-cdn.com/flex013/user_avatar/gov.yearn.fi/miohtama/32/4990_2.png) [@miohtama](https://gov.yearn.fi/u/miohtama)\
**Post date:** [12 December 2025 11:22 UTC](https://gov.yearn.fi/t/what-is-the-status-of-silo-lender-arb-usdc-e/14572/2 "2025-12-12T11:22:23Z")

</div>

With the help of Yearn Discord, I tracked the mutlistrategy assets to Silo V1 USDC e-market. It has 98% utilisation, so this vault might have problems withdrawing and is no longer safe to use - but I hope someone from Yearn can confirm this?

Silo got badly hit in Stream xUSD incident so not sure if this is related.

> **[Silo Finance App](https://v1.silo.finance/silo/0x0696E6808EE11a5750733a3d821F9bB847E584FB)**
>
> Enabling lending and borrowing of any asset

> **[Similar Match Source Code This contract matches the deployed Bytecode of the......](https://arbiscan.io/address/0x0696e6808ee11a5750733a3d821f9bb847e584fb#code)**
>
> Could not find any matches! | Contract: Verified | Balance: $2,132,944.36 across 1 Chain | Transactions: 454 | As at Dec-12-2025 11:21:36 AM (UTC)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/yearn/original/2X/c/c3a1c2d535e564dc49a50437ef69a87842aa91f2.png)

---

<div class="post-metadata">

**Author:** ![dudesahn](https://dub1.discourse-cdn.com/flex013/user_avatar/gov.yearn.fi/dudesahn/32/4350_2.png) [@dudesahn](https://gov.yearn.fi/u/dudesahn)\
**Post date:** [16 December 2025 21:12 UTC](https://gov.yearn.fi/t/what-is-the-status-of-silo-lender-arb-usdc-e/14572/3 "2025-12-16T21:12:12Z")

</div>

it is an isolated market on Silo, lending USDC.e to borrow against ARB collateral—nothing to do with xUSD. High utilization is likely because some other lender withdrew; but no reason to think anything is wrong here. Looks like rates have already started to come down a bit since you posted as well.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/yearn/original/2X/9/9ae7183c96201b2e9a60ad06d0d7664a3e90aeb0.png) [@system](https://gov.yearn.fi/u/system)\
**Post date:** [23 December 2025 21:12 UTC](https://gov.yearn.fi/t/what-is-the-status-of-silo-lender-arb-usdc-e/14572/4 "2025-12-23T21:12:18Z")

</div>

Closed on 23 December 2025 21:12 UTC

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
