The Bitcoin Credit Stack
rates are percent a year, continuously compounded · figures as of 2026-10-15 · read 2026-10-16 04:01 UTC
Market › Algorithmic › Aave v2 › Polygon

Aave v2 (Polygon)

Takes as collateral: bitcoin and ether

aave_v2_polygon · on-chain pool · operated by Aave DAO · registered

One of 3 deployments of Aave v2 · also on Avalanche, Ethereum

Events for this venue: dated moves past a published rule and levels crossed.

Secured by
BTC collateral
61.24 BTC
15% of Aave v2
<0.1% of the market
Dollar debt against bitcoin
$2.3m
whole pool, not its bitcoin book
Aggregate LTV
collecting (not read yet)
Borrow rate (USD loans)
16.83%
+4.56 pts vs Aave v2
Lend rate (USD loans)
0.00%
−0.35 pts vs Aave v2
Liquidation threshold
75.0% LTV
threshold, not a price
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.

  • Dollar debt against bitcoin — the whole pool's lending against every collateral it takes (bitcoin is 25.6% of the pool's collateral) — not debt against bitcoin, and no dollar of it is assigned to bitcoin without an account-level read.
  • Liquidation threshold — the loan-to-value at which the venue liquidates a bitcoin position, not a price: no bitcoin book is read at this venue to turn it into one (a pool's debt has no collateral of its own until its accounts are read).
BTC collateral of Aave v2 — Aave v2 (Polygon) 15%
BTC collateral of Algorithmic — Aave v2 0.3%
Dollar debt against bitcoin of the market — Algorithmic 13%, 13% of its bitcoin collateral

Loan duration is not a venue figure on an on-chain pool: these markets are open-term, and a position runs until it is repaid or liquidated. A fixed term exists only where the venue writes one — the custodial desks (cefi_credit_rates.term_days) and Gavel's auction, which is fixed-rate and fixed-term by construction.

10 of 10 criteria researched. What the criteria are →

Markets — as served, not a venue rate

One row per market, as the venue publishes them. These are market rates: combining them into a single venue rate is a weighting across this venue's markets, and choosing one here would be a methodology decision taken in a web page.

No BTC market rows are served for this venue. It runs contracts, so the absence is this dataset’s, not the venue’s.

Price

What does credit cost here, and how is the price formed?

Rate formationalgorithmic_utilisation
source
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — DefaultReserveInterestRateStrategy, a two-slope function of utilisation: algorithmic_utilisation.
Term structureopen_ended
source
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — borrow()/repay() carry no maturity.
Rate certaintyvariable
source
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — the variable rate follows utilisation through the reserve's strategy 0x333ce9806e7c152a95a307CB27551Af5ae9D4163; v2's stable rate is disabled for WBTC and could in any case be rebalanced. Nothing is fixed at origination.

Quality

What stands behind a position, and what can change under the reader?

Oracle dependencymultiple
source
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — getPriceOracle() = 0x0229F777B0fAb107F9591a41d5F02E4e98dB6f2d (AaveOracle: one source per reserve asset plus a fallback; governance can replace any). A pooled venue's solvency depends on all of them.
Default & liquidationthreshold
source
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — liquidationCall() is permitted once an account's health factor falls below 1, computed from per-reserve liquidation thresholds across its whole collateral (WBTC: LTV 70%, liquidation threshold 75%, bonus 10%).
Custody & backingprotocol_custodial
source
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — deposit() transfers the underlying to the reserve's aToken contract under the pool's control; the depositor holds an aToken claim.
Recoursenon_recourse
source
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — liability is bounded by the account's collateral; no function pursues a borrower beyond liquidationCall().
Track record65 months observed
source
Derived from credit_venues.first_date (2021-04-05), the first Monday on which this dataset's archive read finds bitcoin supplied at the venue (credit_collateral_history) — read from its contracts at past blocks, so near the venue's own start rather than when we began observing. A lower bound on the venue's age. Not typed, and not a claim about its longevity.

Composition

Who and what makes up this market?

Collateral acceptedBTC reserves (1): WBTC
source
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — the WBTC reserve (aToken 0x5c2ed810328349100A66B82b78a1791B101C9D61) holds 62.02 WBTC and is FROZEN (configuration bit 57; borrowing disabled): no new supply or borrowing, existing positions remain and can be liquidated. NOTE: the venue is POOLED and multi-collateral, so a BTC reserve's presence does not mean a given borrow is secured by it.
Book depth & concentrationunknown (no per-venue counterparty count exists in this registry or in the comparison payload, so depth and concentration cannot be established. This is a gap in THIS DATASET, not in the venue, and is a different value from `undisclosed`, which would mean the venue does not publish it.)
Observability
price: none — Not observed: this venue's rates are not read. It is registered for its collateral history.
quantity: partial — Observed through the venue's own contracts: the supplied amount of its bitcoin reserve, read DAILY at a recorded block since 2026-10-01 and WEEKLY at past blocks back to 2021-04-05. Collateral only — the venue's debt is not read.
composition: none — Not observed: composition is loan-level.

What the loans are denominated in

Not yet established for this venue — which is not the same as dollars.

Backing chain

Each link from what this venue takes as collateral down to the bitcoin it rests on, in order, with how each link was established.

How a chain is read, and what it does not claim

backing_chain: the ordered claims standing between a creditor and the coins, each link derived from a sourced fact already held and carrying it in `derived_from` — the custody cell, the venue's borrow card, or wrapper_registry.yaml for who holds the bitcoin behind a token. A `representation` link has one branch per token the venue takes; branches are alternatives, not a sequence. A link nobody has established is shown with status `incomplete` and names what is missing — it is never dropped, because a missing link omitted makes a long chain look short. `undisclosed` means the party does not publish it; `incomplete` means this dataset has not established it. NEVER SCORED AND NEVER COUNTED: no length, link count or ranking is published, and none should be derived — chain length and link transparency are orthogonal (ETP-backed margin is the longest chain here and every link of it is regulated). `recourse` is what the creditor holds beyond the chain. ⚠ Tokens are identified BY SYMBOL: the wrapper registry is not keyed by chain or address, so every `representation` link carries a `deployment` step that is incomplete — whether a token is native to the chain of the venue or a bridge receipt (one more link) is not established — and a symbol the registry knows to name a different token on a venue is shown unresolved, not given that wrapper's holders.

  1. contract_escrow established — the protocol contract — the collateral is escrowed and neither the operator nor the borrower can move it
    source
    attribute · custody_model = protocol_custodial
    Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — deposit() transfers the underlying to the reserve's aToken contract under the pool's control; the depositor holds an aToken claim.
  2. representation incomplete
    source
    wrapper_registry · wrapper_registry.yaml as of 2026-09-02
    deployment · chain 137 incomplete
    whether each token is issued natively on this chain or bridged to it — a further link when bridged — is not in wrapper_registry.yaml, which is keyed by symbol, not by chain or address
    • WBTC established · direct_wrapped · identified by symbol
      WBTC established · issuer BitGo · custodial · holders [BitGo]
      Reserves in 2-of-3 multisig with BitGo holding two keys. Since 2024 BitGo custodies jointly with BiT Global, a Hong Kong custodian part-owned by Justin Sun — a second name on the same bitcoin, recorded but not split because no share is published.
      source
      issuer_doc
      BitGo, 'Wrapped BTC Launches with BitGo Custody and Full Proof of Assets', blog.bitgo.com; proof-of-reserve at wbtc.network
Recourse: non_recourse
source
attribute · recourse
Aave v2 LendingPool 0x8dFf5E27EA6b7AC08EbFdf9eB090F32ee9a30fcf on Polygon PoS (chain 137), addresses provider 0xd05e3E715d945B59290df0ae8eF85c1BdB684744, read at block 94762881 (registry/resolution/2026-10/historical_cells.json) — liability is bounded by the account's collateral; no function pursues a borrower beyond liquidationCall().

The generic axis set

Identical for every venue, identically computed. An axis that cannot be computed here renders its reason — never silently omitted, because an omitted axis says it was not considered. A figure that covers only part of what the axis asks is marked, with what it leaves out beneath it. Collateral, debt and the borrow and lend rates are the tiles at the top of this page.

Utilisation (venue roll-up)41.1%
the pool's dollar reserves: borrowed over supplied across 3 reserve(s), on 2026-10-16 — the whole pool, not its bitcoin book
our daily direct read of the venue's contracts; not compared against a second series; quantity-gated
Intermediation margin+16.83 pts · derived
the pool's borrow rate minus its supply rate on the same dollar reserves — what the venue keeps, plus the cost of idle supply
borrow rate minus lend rate, both as above
Trailing realised average (7/30/90d)7d 17.24% · 30d 16.86% · 90d 16.65%
dollar loans, debt-weighted over the days observed (7 / 30 / 90 of 7 / 30 / 90); continuously compounded; fully drawn pools' rates (99.5% or more drawn) left out
mixed: our daily direct read of the venue's contracts; not compared against a second series; block-instant read from the venue's contracts (not a daily mean) — the 30-day window's gates and $250k floor
Rate volatility (30/90d)30d 0.32 pts · 90d 0.24 pts
the standard deviation of the daily debt-weighted borrow rate, in percentage points — not annualised
the daily rate above
Spread to the pair aggregate+12.10 pts vs Algorithmic · derived
this venue's borrow rate minus its class's (4.73%), both as served on the spine
/v1/market/tree — the venue's and its class's borrow rates
Spread to matched Treasuries+12.73 pts vs the 1-month bill (4.10%) · derived
the venue's borrow rate minus the 1-month bill, both continuously compounded. An open-term loan has no maturity of its own, so the bill stands for a 30-day window
macro_rates — the 1-month Treasury bill, 2026-10-14 (Federal Reserve H.15)
Origination flowcollecting (not read yet) — loan events are read for Morpho Blue (Ethereum, Base) and the six Aave v3 chains only
Repayment flowcollecting (not read yet) — loan events are read for Morpho Blue (Ethereum, Base) and the six Aave v3 chains only
Aggregate and distributional LTVcollecting (not read yet) — a historical venue: its bitcoin collateral is read from its own contracts each day; its debt is not read yet
Residence distributioncollecting (not read yet) — how long positions stay open needs each loan's history; it is held for Morpho Blue and the Aave v3 chains and not yet computed
Liquidation incidencecollecting (not read yet) — liquidations are read from events for Morpho Blue and the Aave v3 chains, and as positions past threshold where a pool is read account by account
Top-10 concentration sharecollecting (not read yet) — borrower concentration is read where a pool is read account by account (21 venues)

Source: Board of Governors of the Federal Reserve System (H.15, H.4.1, H.6).

There is no score on this page and none will be added. The criteria are published and versioned before any venue is measured against them, and this venue's row is produced by the same pipeline as every other.

Access routes

Unknown (not surveyed yet). No one has looked for an MCP server for this venue. That is not the same as having looked and found none, and this row will not say the second while meaning the first. The listing criteria are published.

Ask for this by machine

REST
GET https://api.bitcoincreditstack.com/v1/market/venues/aave_v2_polygon
MCP
get_venue({ venue_id: "aave_v2_polygon" })
get_venue({ venue_id: "aave_v2_polygon", include: ["axes", "headline"] })

The same figures, the same names and dates. Connect your AI →

Ask your own question about this venue
read-only MCP · zero write tools · no account

How this venue compares depends on what you'd borrow, for how long, against what. That's a question for your AI, with this data behind it.

Orientation · Aave v2 (Polygon)Holder · Aave v2 (Polygon)Treasurer · Aave v2 (Polygon)Analyst · Aave v2 (Polygon)Risk · Aave v2 (Polygon)
Add to Claude ↗Connect in Cursor ↗Connect in VS Code ↗Add to ChatGPT ↗Add to Grok ↗or copy the MCP URLhttps://mcp.bitcoincreditstack.com/mcp