Compound v3
One protocol, deployed on 6 chains. Each deployment is a separate set of contracts with its own book, collateral list and parameters, so each keeps its own page and its own figures. The rows are not added together here.
| Deployment | Venue type | Status | BTC collateral | Debt | LTV | Borrow rate | Criteria researched |
|---|---|---|---|---|---|---|---|
| Arbitrum › | onchain_pooled | registered | 409 BTC | — | — | — | 2/10 |
| Base › | onchain_pooled | registered | 114 BTC | — | — | — | 2/10 |
| Ethereum › | onchain_pooled | registered | 6,927 BTC | — | — | — | 10/10 |
| Optimism › | onchain_pooled | registered | 55 BTC | — | — | — | 2/10 |
| Polygon › | onchain_pooled | registered | 43 BTC | — | — | — | 2/10 |
| Scroll › | onchain_pooled | registered | — | — | — | — | 2/10 |
Sorted by venue id, not by any figure. Figures are each deployment's own headline read (5 of 6 deployments have one), as of 2026-09-21; a dash carries its reason on hover. get_venue · list_venues
What a family is, and is not
A family is the presentation parent of a venue: one protocol across its chain deployments (Aave v3 on Ethereum, Arbitrum, Base…), one corporate issuer, or one desk. family_id matches the ids other payloads use (the corporate issuer_id, the rate-card desk key). It is NOT a measurement unit: every figure in this dataset keys on venue_id, and a family lists its venues rather than summing them. Deployments of one family are separate contracts with separate books and can differ in collateral, parameters and risk.