Oracle and contract risks
Understand v24 source, custody, configuration, and execution risks.
Oracle risk
An oracle can be stale, unavailable, outside price limits, or too uncertain. Calendar closure, reopen grace, and sequencer protection add action restrictions. A fresh update does not guarantee an executable trade or a healthy account. DEX TWAP quality depends on the approved source, observation window, and liquidity.
Oracle rotation requires both sources and guarded governance checks. It is not a promise to restore exits immediately when the current source fails.
Contract and identity risk
v24 pools use immutable implementation proxies, but configurable policy and authorized Router bindings still matter. Pool, Account, Router, Lens Set, collateral, and oracle identities must match. Do not substitute an older ABI or Lens when a v24 read fails.
Quotes describe a particular state and do not reserve it. A transaction may revert after another action changes accounting, custody, configuration, or the oracle price. An unavailable read is not a zero balance or proof of safety.
Collateral and custody risk
Custody checks distinguish actual token balances from recorded liabilities. The exact collateral-transfer boundary rejects failed transfers, malformed token returns, or mismatched sender and receiver balance changes. The entire action reverts; the failed action does not silently convert its payment into successful escrow or persist an incident flag.
Token pauses, blocklists, transfer taxes, or balance changes can prevent supported transfers. Incident recording and remediation are separate guarded operations. Repaying debt, covering a custody deficit, covering uncovered loss, and providing recovery capital solve different accounting problems.
When a tcUSD depeg monitor is bound, its state can restrict new risk and other dependent actions. Healthy price-position arithmetic alone does not override collateral-policy restrictions.
Operational availability
A committed contract or recorded testnet deployment does not prove the app, keeper, indexer, or reward campaign is enabled. Check the chosen network's published integration. This documentation explains protocol behavior, not an assurance of current production availability.