Silo Finance primary sources — 2026-05-08

Classification takeaway

Silo Finance is best classified as permissionless isolated lending-market infrastructure with an explicit lender-protection fallback, not just another isolated-pool money market. The key mechanism is the combination of one-sided market isolation and a second liquidation engine — collateral-debt swap (CDS) defaulting — that writes off debt internally and reimburses lenders with collateral share tokens when normal market-sale liquidation becomes unreliable.

Primary sources reviewed

1. Official site — https://www.silo.finance/

   • Markets Silo around isolated lending, higher yield, and lender protection.
   • Useful mainly as the current product framing: liquidation fees, collateral upside, borrower interest, and “protection against bad debt” are treated as core selling points.

2. User intro docs — https://docs.silo.finance/docs/users/intro/

   • Gives the cleanest high-level statement of the v3 thesis.
   • Says Silo v3 is designed to guarantee lender solvency without relying on instant liquidity.
   • Identifies three pillars: risk-isolated markets, a dual liquidation system including CDS, and guaranteed lender coverage even when liquidation liquidity is unavailable.

3. Isolated pairs docs — https://docs.silo.finance/docs/users/core-concepts/silo/isolated-pairs/

   • Explains that each market is a one-sided pair of single-asset vaults.
   • Important for classification because it makes the risk container explicit: lenders in one market are exposed only to that market’s collateral and borrower setup.
   • Shows the protocol is not simply “isolated by asset listing” but structurally separated market by market.

4. Lender protection / liquidation docs — https://docs.silo.finance/docs/users/core-concepts/silo/liquidation/

   • Most important mechanism source in this pass.
   • Describes the two liquidation paths: standard collateral-sale liquidations and internal collateral-debt swap (CDS) defaulting.
   • Explains that in CDS, debt is written off at the accounting level and lenders are compensated with collateral share tokens via an Incentive Controller rather than via a forced DEX sale.
   • Notes that CDS can coexist with standard liquidations, uses lower liquidator incentives, and may be configured with restricted executors, which makes the fallback path itself a governance/control surface.

5. Developer architecture docs — https://docs.silo.finance/docs/developers/protocol-overview/architecture/

   • Confirms each market is composed of two ERC-4626 vaults and is permissionless to deploy through Silo Factory.
   • Says markets are immutable by default unless deployers opt into upgradable settings.
   • Adds important mechanism detail on borrowable vs protected collateral, hooks-based extensibility, per-asset oracle configuration, and the PI-controller-style dynamic interest-rate model.
   • Useful because it makes clear that Silo is a configurable framework, not just a single lender-facing app.

6. Risk disclosures — https://docs.silo.finance/docs/security/risks/

   • Important corrective source.
   • Explicitly says risk is localized, not eliminated, and that lenders underwrite the borrower + collateral + oracle + liquidity conditions of the specific market they enter.
   • Helps prevent over-reading the stronger “guaranteed solvency” marketing language as literal risk removal.

7. Public contracts repository — https://github.com/silo-finance/silo-contracts-v3

   • Confirms the live protocol architecture is exposed as a public V3 contracts monorepo.
   • Useful for validating that market deployment, hooks, and configuration are first-class protocol surfaces rather than only documentation abstractions.

8. Repository README — https://raw.githubusercontent.com/silo-finance/silo-contracts-v3/develop/README.md

   • Shows the project is organized around deployable market configs and local deployment scripts.
   • Reinforces that the protocol is meant to support repeated market deployment rather than one centrally curated pool set.

Whitepaper / technical-doc status

• No single canonical standalone whitepaper or litepaper stood out clearly in this pass.
• The docs are strong enough to classify the mechanism without one, especially the intro, liquidation, architecture, and risk pages.
• If this becomes a deeper comparison target, the next step should be pulling more contract-level docs around CDS, hooks, factory deployment choices, and oracle configuration.

Why it stays in the active corpus

• Good comparison class for Blend, Euler, Morpho, and Wildcat because it moves the control surface away from one global risk engine in a different way.
• Distinctive for pairing isolated markets with an explicit debt-writeoff-and-collateral-reimbursement fallback instead of relying only on external liquidation liquidity.
• Useful for future work on where practical authority sits when deployers choose market configs, oracle setups, liquidation thresholds, and optional executor restrictions while lenders still face localized but non-zero underwriting risk.