DeFi / lending mechanics and risk

DeFi lending: collateral, oracles and liquidation

Understand collateralized borrowing and its price inputs with a solved fictional example; no account, pool or current market is assumed.

Documentation checked: 2026-10-26 · Edition 1.0 · 5 min read

You will learn

Trace supplied collateral, borrowed debt, oracle input and liquidation conditions as separate protocol records.
Explain why borrow capacity and a liquidation threshold are distinct, protocol-specific measures.
Recompute the fictional collateral, debt, borrow-limit, LTV and health-ratio example with its stated assumptions.
Identify oracle, contract, governance and liquidation uncertainties without treating the model as a borrowing recommendation.

Before you begin

No account, wallet, funds or transaction is needed. Every parameter, asset, price and debt amount in the worked example is fictional; no Venus market values are used.

Separate collateral, debt and a lending market

A collateralized lending protocol records supplied collateral and a separate borrowed asset as a debt. A protocol applies market-specific parameters and an oracle-derived value to calculate borrowing capacity; interest or other contract terms can change the debt. This differs from a Binance Spot balance and from providing two assets to an AMM liquidity pool.

Venus documentation is used here as one protocol-specific reference relevant to BNB Chain. Its supply guide describes supplied assets, borrow limits and market caps; it does not establish that a market is active, available to a particular user, or suitable for anyone. No app, account, wallet, market, contract or transaction was accessed.

Evidence: Venus supply and borrow model · Venus market registry and availability limits

Describes Venus documentation, not every lending protocol or an available market. It is not evidence of current account eligibility, rates, pool liquidity or permission to interact.

A documentary registry, not a live account or contract check. On the page read 2026-10-26, Venus labels non-Core mainnet isolated pools on BNB Chain, Ethereum and Arbitrum Legacy / exit-only. This dated page is not proof that any specific market is currently available.

Borrowing power and liquidation threshold answer different questions

A collateral factor (CF) is one protocol parameter for how much supplied value can support borrowing. A liquidation threshold (LT) describes when the protocol may treat an account as under-collateralized. The definitions and formula differ across protocols. Venus states that CF and LT coincide in its Core Pool while they may differ in Isolated Pools; do not apply that relationship outside the named protocol or its documented pool.

The table is a definition check, not a current parameter list. A symbol in a user interface or a general protocol page does not prove an asset is enabled as collateral or that borrowing is available.

Protocol terminology; no live market parameters were checked.
Measure	Question it models	Boundary
Collateral factor (CF)	Which fraction of supplied collateral value counts toward borrow power?	May vary by asset, market and protocol.
Liquidation threshold (LT)	At which value condition can under-collateralization make liquidation possible?	Eligibility, thresholds and execution rules are protocol-specific.
Oracle inputs	Which price is used for collateral and debt valuation?	Source, freshness, fallback and configuration need separate evidence.

Evidence: Venus collateral factors and liquidation thresholds · Venus price-oracle roles and limits

Venus-specific model: its page says CF and LT are the same in Core Pool and may differ in Isolated Pools. Do not generalize its functions, thresholds, eligibility or minimums to another protocol or a present account.

This page describes the Venus V4 design. It says multiple independent sources are not guaranteed for every asset and source roles, addresses and bounds can change. It is not proof that a deployed market has independent feeds or a healthy price.

Recompute a fictional borrowing and risk check

All values below are invented teaching assumptions, not Venus values, a price quote or a recommendation. Assume a fictional protocol uses a CF of 60% and a distinct LT of 75%; one DEBT unit is assigned one fictional accounting unit; there are no fees, slippage, liquidation incentive or other collateral. The later debt of 105 is simply assumed to include 5 units of fictional accrued interest; no rate or time calculation is implied.

At the start, 2 COLL at 100 units each gives collateral value 200. The illustrative borrow limit is 200 x 60% = 120 DEBT units. A debt of 100 is 100 / 200 = 50% LTV and below that simplified limit. The LT value is 200 x 75% = 150, so the simplified health ratio is 150 / 100 = 1.50.

At the later fictional check, COLL is assigned 60 units, so collateral value is 2 x 60 = 120. Assumed debt is 105. Borrow power under the same fictional CF is 120 x 60% = 72; the simplified LT value is 120 x 75% = 90. LTV is 105 / 120 = 87.5%, and the simplified health ratio is 90 / 105 = 0.857. The arithmetic flags potential liquidation conditions under these assumptions; it does not predict that a real protocol will liquidate an account.

Solved example in invented units; not a real account, token, market or price.
Measure	Start: fictional	Later: fictional	Recheck
Collateral value	2 COLL x 100 = 200 units	2 COLL x 60 = 120 units	quantity x assumed unit value
Debt	100 DEBT units	105 DEBT units	later amount includes a fictional 5-unit increase
CF borrow limit	200 x 60% = 120 DEBT	120 x 60% = 72 DEBT	collateral value x CF
LT value	200 x 75% = 150 DEBT-equivalent	120 x 75% = 90 DEBT-equivalent	collateral value x LT
LTV	100 / 200 = 50%	105 / 120 = 87.5%	debt / collateral value
Simplified health ratio	150 / 100 = 1.50	90 / 105 = 0.857	LT value / debt; below 1 is a risk flag in this invented model

Evidence: Venus collateral factors and liquidation thresholds

An oracle is an input, not a guarantee of the market price

A lending protocol cannot infer every external token price from its own contract state. An oracle supplies price inputs used by protocol calculations. A stale, erroneous or manipulated input can distort borrowing power or liquidation checks.

Venus documents a configurable ResilientOracle with per-asset main, pivot and fallback roles. The documentation explicitly says this does not guarantee multiple independent sources for every asset: if a pivot is not configured or enabled, a valid main response can be used without cross-validation. Governance may change source addresses, roles, enable flags and bounds. This is a description of Venus documentation, not evidence of the current configuration for a deployed market.

Evidence: Venus price-oracle roles and limits

Liquidation and contract controls add separate risks

In the Venus-specific documentation, liquidation means collateral can be seized to repay outstanding debt when an account is under-collateralized. The docs distinguish CF and LT, say the Core Pool uses the same value for both, and state Isolated Pools can differ. Actual eligibility may also depend on a market-specific minimum, oracle result, pause flags and other deployed rules; crossing a simplified line is not proof that a liquidation occurred.

Protocol code, proxies, governance permissions, market caps and pause settings create software and administration risks. Venus market documentation warns that its address registry is not a guarantee of current market actions and that configuration and implementations can change. A documentation page or audit label is not a guarantee that a deployed version is safe or unchanged.

Evidence: Venus collateral factors and liquidation thresholds · Venus market registry and availability limits

List the unknowns before relying on a lending claim

For a specific claim, a read-only review would need the exact network, protocol and market; token contracts and price units; current CF/LT and borrow/supply status; oracle source roles and freshness; debt accrual and liquidation rules; relevant contracts, proxy implementation and governance controls. The official registry itself may be descriptive rather than live.

No account, wallet, funds, signature, market state, oracle feed, address or deployed contract was checked for this guide. No pool or product is assumed available. The worked case cannot establish personal suitability, legal or tax treatment, likely returns or future price movement.

Price can move or be reported incorrectly.
Debt can grow under terms that must be read exactly.
A contract defect, privileged change, pause, liquidity constraint or liquidation can change the outcome.
This page does not recommend borrowing or supply; keep the example as arithmetic only.

Evidence: Venus supply and borrow model · Venus price-oracle roles and limits · Venus market registry and availability limits

Describes Venus documentation, not every lending protocol or an available market. It is not evidence of current account eligibility, rates, pool liquidity or permission to interact.

Check your understanding

In the fictional case, what does the later ratio of 90 / 105 = 0.857 establish?

Show explanation

Only that the invented LT-value-to-debt ratio is below 1 under the stated fictional assumptions, which flags potential liquidation conditions in that simplified model. It does not prove that any real account exists, is liquidatable or will be liquidated.

Primary sources

Supplying and borrowingVenus Protocol documentation · 2026-10-26
Describes Venus documentation, not every lending protocol or an available market. It is not evidence of current account eligibility, rates, pool liquidity or permission to interact.
LiquidationsVenus Protocol documentation · 2026-10-26
Venus-specific model: its page says CF and LT are the same in Core Pool and may differ in Isolated Pools. Do not generalize its functions, thresholds, eligibility or minimums to another protocol or a present account.
Resilient Price OracleVenus Protocol documentation · 2026-10-26
This page describes the Venus V4 design. It says multiple independent sources are not guaranteed for every asset and source roles, addresses and bounds can change. It is not proof that a deployed market has independent feeds or a healthy price.
MarketsVenus Protocol documentation · 2026-10-26
A documentary registry, not a live account or contract check. On the page read 2026-10-26, Venus labels non-Core mainnet isolated pools on BNB Chain, Ethereum and Arbitrum Legacy / exit-only. This dated page is not proof that any specific market is currently available.