Lending yield comes from borrower demand and incentives, not a fixed return.
Suppliers avoid borrower liquidation risk directly but still face market, contract, oracle and liquidity risk.
Key takeaways
- Supply and collateral are different roles. A deposited asset may earn interest or secure borrowing depending on product design.
- Borrowing creates a health constraint. Falling collateral or rising debt can trigger liquidation.
- Receipt assets represent positions. Their integrations add composability and dependency.
- High utilization affects exits and rates. Available pool liquidity matters when users withdraw.
How rates move
Utilization links supply and borrow demand. Incentive tokens can temporarily raise displayed yield, so compare base interest with subsidies and model what happens when rewards end.
Borrower checklist
Monitor health factor, oracle prices and liquidation thresholds; leave a volatility buffer; understand interest accrual; keep gas and a repayment path available.
Supplier checklist
Check asset quality, pool liquidity, contract addresses, audits, governance controls and the exact claim represented by any receipt token.
A decision framework
Before using, integrating or promoting the product, reproduce its central user journey with a small test. Record the contracts, permissions, counterparties and fees involved. Then model four failures: the interface disappears, an operator stops responding, market liquidity falls and an administrator uses an emergency power.
A credible decision identifies who can change the system, what evidence confirms the result and how a user exits without relying on promotional promises. Recheck these facts against current primary documentation because Web3 products, contracts and operating entities can change faster than an indexed article.
Crynet helps Web3 teams turn complex products into evidence-led decisions through relevant strategy and communication.
Sources
This article is educational and is not financial, legal or investment advice.
