Aave v2 (Avalanche)
One of 3 deployments of Aave v2 · also on Ethereum, Polygon
Hover a figure for its basis and read. The market and every class, family and venue carry these same three, chosen by the published definitions, as of 2026-10-01. What each one measures →
Quantities are a contract-state read. No liquidation price is derived: no liquidation threshold (LLTV) is ingested for this venue. Its own documentation may publish one; this dataset does not read it, so no price is derived. That is a coverage gap in this estate, not a property of the venue. this venue pools borrowing across every collateral it accepts, so no BTC-specific debt exists to read — the contract-state rows carry debt_attribution 'unavailable' and no dollar figure. A market-wide borrow total would be a number about this venue, not about its bitcoin book, and it is not served as one.
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. Serving "duration: none" for a pool would read as a missing measurement rather than a property of the instrument.
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 formation | algorithmic_utilisationsourceAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (registry/resolution/2026-10/historical_cells.json) — DefaultReserveInterestRateStrategy, a two-slope function of utilisation: algorithmic_utilisation per v1 §8.2. |
|---|---|
| Term structure | open_endedsourceAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (registry/resolution/2026-10/historical_cells.json) — borrow()/repay() carry no maturity. |
| Rate certainty | variablesourceAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (registry/resolution/2026-10/historical_cells.json) — the variable rate follows utilisation through the reserve's strategy 0xD9Dee878Eb31303FD58D412cE79439400b340A22; v2's stable rate is disabled for WBTC.e 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 dependency | multiplesourceAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (registry/resolution/2026-10/historical_cells.json) — getPriceOracle() = 0xdC336Cd4769f4cC7E9d726DA53e6d3fC710cEB89 (AaveOracle: one source per reserve asset plus a fallback; governance can replace any). A pooled venue's solvency depends on all of them. |
|---|---|
| Default & liquidation | thresholdsourceAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (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.e: LTV 0%, liquidation threshold 70%, bonus 5%). |
| Custody & backing | protocol_custodialsourceAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (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. |
| Recourse | non_recoursesourceAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (registry/resolution/2026-10/historical_cells.json) — liability is bounded by the account's collateral; no function pursues a borrower beyond liquidationCall(). |
| Track record | 59 months observedsourceDerived from credit_venues.first_date (2021-10-04), the first Monday on which this dataset's archive read finds bitcoin supplied at the venue (credit_collateral_history, migration 152) — 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 accepted | BTC reserves (1): WBTC.esourceAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (registry/resolution/2026-10/historical_cells.json) — the WBTC.e reserve (aToken 0x686bEF2417b6Dc32C50a3cBfbCC3bb60E1e9a15D) holds 67.98 WBTC.e and is FROZEN (configuration bit 57; borrowing disabled): no new supply or borrowing, existing positions remain and can be liquidated, and at LTV 0 it gives no new borrowing power. NOTE: the venue is POOLED and multi-collateral, so a BTC reserve's presence does not mean a given borrow is secured by it (v1 §6.4). |
|---|---|
| Book depth & concentration | unknown (no per-venue counterparty count exists in this registry or in the comparison payload, so depth and concentration cannot be established (OB2-F1). 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 (criteria §0.6).) |
| 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 migration 153 and WEEKLY at past blocks back to 2021-10-04 (migration 152). Collateral only — the venue's debt is not read. composition: none — Not observed: composition is loan-level. |
Backing chain
backing_chain (v1 §9.5, D29): 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.
- 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_custodialAave v2 LendingPool 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C on Avalanche C-Chain (chain 43114), addresses provider 0xb6A86025F0FE1862B372cb0ca18CE3EDe02A318f, read at block 96521831 (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. - representation incomplete
source
wrapper_registry · wrapper_registry.yaml as of 2026-09-02deployment · chain 43114 incompletewhether 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.e established · direct_wrapped · identified by symbolWBTC.E established · issuer BitGo · custodialWBTC bridged to Avalanche — BitGo custody plus the Avalanche Bridge.
source
issuer_docinherits WBTC's sourcingWBTC 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_docBitGo, 'Wrapped BTC Launches with BitGo Custody and Full Proof of Assets', blog.bitgo.com; proof-of-reserve at wbtc.network
- WBTC.e established · direct_wrapped · identified by symbol
source
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.
| Collateral locked | not available — this venue has no market rows in the rates payload yet |
|---|---|
| Debt outstanding | not available — this venue has no market rows in the rates payload yet |
| Utilisation | not available — this venue has no market rows in the rates payload yet |
| Venue-level borrow APR | not available — this venue has no market rows in the rates payload yet |
| Venue-level lend APR | not available — this venue has no market rows in the rates payload yet |
| Intermediation margin | not available — this venue has no market rows in the rates payload yet |
| Trailing realised average (7/30/90d) | not available — no per-venue time series is held, so a trailing figure would be a single reading dressed as an average |
| Rate volatility (30/90d) | not available — no per-venue time series is held, so a trailing figure would be a single reading dressed as an average |
| Spread to the pair aggregate | not available — this venue has no market rows in the rates payload yet |
| Spread to matched Treasuries | not available — this venue has no market rows in the rates payload yet |
| Origination flow | not available — needs loan-level history, which is held for Morpho Blue only |
| Repayment flow | not available — needs loan-level history, which is held for Morpho Blue only |
| Aggregate and distributional LTV | not available — needs loan-level history, which is held for Morpho Blue only |
| Residence distribution | not available — needs loan-level history, which is held for Morpho Blue only |
| Liquidation incidence | not available — needs loan-level history, which is held for Morpho Blue only |
| Top-10 concentration share | not available — needs loan-level history, which is held for Morpho Blue only |
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
Not yet surveyed. 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.
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.
https://mcp.bitcoincreditstack.com/mcp