defi lending · Global

Silo Finance

Risk-isolated non-custodial DeFi lending protocol. Silo experienced a November 2023 GRAIL/USD oracle mispricing event that liquidated three users, while the protocol remained operational and later advanced to Silo v3, live on Ethereum, Arbitrum, and Avalanche in 2026.

Also known as: Silo, Silo Protocol, Silo v3

Status
Active
Outcome
Unknown
Confidence
High
Last verified
2026-09-02
Launch
End
Failure reasonUnknown
Events1
Evidence3
Products1

Case summary

What happened

On 2023-11-22, GRAIL/USD pricing used by a Silo Arbitrum market deviated after anomalous HTX trading data entered DIA's feed. Three users became insolvent and were liquidated, with Silo governance reporting roughly USD 21,000 in liquidation losses/fees. DIA removed HTX as a source and tightened deviation controls. A later proposal to compensate the affected users in SILO tokens was defeated. Silo continued operating and Silo v3 remained live in 2026.

Customer result

Customer outcome

Unknown

Silo governance discussed compensating the three affected users with SILO tokens, but the proposal was defeated. CYA therefore does not record realized compensation or a recovery percentage. The incident did not establish a protocol-wide claims process.

Estimated recovery
Unknown
Repayment started
Repayment completed
Confidence
High

Asset treatment

Terms risk

Customer-owned

Silo is modeled as non-custodial smart-contract lending rather than a platform-owned account balance. The November 2023 event demonstrates third-party oracle and liquidation risk in isolated lending markets; non-custodial architecture does not remove those economic risks or guarantee compensation for oracle-driven liquidations.

Affected product
Confidence
High

Source: Introduction to Silo v3

Known unknowns

Uncertainty

The roughly USD 21,000 figure is the governance post's estimate of losses associated with the three liquidations, not a protocol-wide bad-debt figure. The defeated compensation proposal is not treated as realized recovery.

Chronology

Historical record

price manipulationMedium impact2 sources

Silo GRAIL oracle deviation liquidates three users

The DIA GRAIL/USD feed used by a Silo Arbitrum market incorporated anomalous HTX trading data during a broader exchange incident, causing the reported price to deviate materially from the perceived market value. Three users became insolvent and were liquidated. Silo governance estimated roughly USD 21,000 in losses associated with the liquidations. DIA removed HTX as a source and tightened deviation thresholds after the incident.

This is an oracle-data incident, not evidence of a protocol-wide exploit or insolvency. The approximately USD 21,000 figure is not represented as protocol bad debt.

Source record

Evidence dossier

Filter by claim, reliability, source type, and whether evidence is linked to a specific event.

Showing 3 of 3 evidence records

Event

2 sources
community referenceMediumEvent linked

DIA Oracle misreported GRAIL/USD price - November 22nd 2023

Silo Governance · 2023-11-27

Primary Silo governance incident thread documenting the November 22 GRAIL/USD feed deviation, three liquidated users, roughly USD 21K in losses, DIA mitigation, and the later defeated compensation proposal.

Official statementHighEvent linked

CDR #042: Silo Finance | Price Feeds

DIA · 2023-11-23

Oracle-provider disclosure describing the GRAIL feed deviation, removal of HTX as a data source, and tightened deviation thresholds.

status

1 sources
Official statementHigh

Introduction to Silo v3

Silo Finance · 2026-04-02

Current Silo documentation stating Silo v3 is live on Ethereum, Arbitrum, and Avalanche.

Comparative records

Independent archive

Help maintain customer-outcome records

Support court-document review, source preservation, corrections, broken-link replacement, and long-term archive maintenance. Support does not influence classifications or evidence standards.

Support CYA

Record maintenance

Report this record

Report incorrect dates, status, customer outcome, terms-risk interpretation, URL history, or missing evidence.

Submit correction →