Dolomite
Dollar loans only: other currencies are separate books, never added in
Debt and rates count loans made in US dollars and dollar stablecoins. Loans in euros, francs, yen, ether or bitcoin itself are separate books, shown by currency on each venue, never added in.
What these figures cover — and what they leave out
- BTC collateral — part of it is the supplied amount each pool reports, not what is pledged against a loan.
- Dollar debt against bitcoin — the pools' whole lending against every collateral they take — not debt against bitcoin, never added to a bitcoin total.
- Liquidation threshold — the range of the liquidation thresholds set by 3 of 3 deployments; no bitcoin book here is read to turn them into a price.
| Deployment | BTC collateral | share | Dollar debt against bitcoin | share | LTV | Borrow | Lend | Liquidates at | Threshold (LTV) |
|---|---|---|---|---|---|---|---|---|---|
| Ethereum › | 7.75 BTC | 11% | $319m | — | 4.76% | 2.77% | — | 85.0% LTV | |
| Arbitrum › | 55.73 BTC | 78% | $2.9m | — | 7.80% | 4.41% | — | 87.0% LTV | |
| Berachain › | 8.19 BTC | 11% | $2m | — | 5.94% | 3.66% | — | 87.0% LTV |
Ordered by debt, never by a rate; a figure in italics covers part of a book
Ordered by debt against bitcoin, then collateral — never by a rate. Shares are of this family's total, and add up. A figure in italics covers only part of a book — hover for what it leaves out; a dash carries its reason. 3 lend from a pool against every collateral, report a whole book, or are financed without a lien: their figures are shown on their rows and not added ($324m in all). /v1/market/tree
One protocol, deployed on 3 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 | Criteria researched |
|---|---|---|---|
| Arbitrum › | on-chain pool | ingesting | 10/10 |
| Berachain › | on-chain pool | ingesting | 10/10 · listed |
| Ethereum › | on-chain pool | ingesting | 10/10 |
Sorted by venue id, not by any figure. Figures are each deployment's own headline read (3 of 3 deployments have a collateral or debt figure), as of 2026-10-15; a dash carries its reason on hover, and a figure in italics covers only part of the bitcoin book — hover for what it leaves out. 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.
Ask for this by machine
| REST | GET https://api.bitcoincreditstack.com/v1/market/venues |
|---|---|
| MCP | list_venues() get_venue({ venue_id: "dolomite_arbitrum" }) |
The same figures, the same names and dates. Connect your AI →