Oracles composability and contract risk

EN source master · P11-L07 · 30 minutes estimated · needs_review

Offline formative study. No wallet connection, real funds, private keys, signatures, live trade or personal portfolio inputs. Visuals are specifications; this is neither runtime content nor certification.

A contract can follow its code exactly while consuming stale, mismatched or economically fragile inputs.

Read the feed's meaning

Data feeds aggregate inputs and publish updates; consumers, proxy and aggregator form separate dependencies [ORACLE]. Record asset pair, network, decimals, update time, round and source methodology. A feed number is not an infallible valuation, and a proxy can introduce upgrade dependencies.

Apply the declared consumer check

Our fictional consumer accepts age≤60 seconds, requiring correct pair and decimals. At observationT1000, last updateT900 gives age100 and fails freshness. A fictional heartbeat120 does not override the consumer's60-second policy. Real feed updates can follow deviation and heartbeat conditions and face network delay; they are not continuous tick streams.

Separate pool spot from reference history

A spot reserve ratio can move sharply with a local swap. The v2 whitepaper discusses accumulated time-weighted price observations and the freshness-versus-manipulation tradeoff [V2]. A TWAP is a sampled method, not proof against every manipulation or stale market. Multiple feeds can share providers, so apparent redundancy need not mean independence.

Trace failure propagation

The original dependency chain is wrapped asset→redemption contract→oracle→lending threshold→liquidation exit pool. At each edge, ask which conversion or assumption is used. A redemption outage can undermine oracle meaning even if updates continue. An audit's scope, code version and date matter, and an audit does not guarantee safety. The offline exercise maps conditions; it supplies no executable attack or contract interaction.

• Freshness: age of last supplied observation relative to a consumer policy.
• Heartbeat: update trigger interval, not continuous streaming.
• Composability: one component's output becomes another's input.
• TWAP: time-weighted price estimate with a declared window.

ILLUSTRATIVE consumerT1000,feed updatedT900,heartbeat120,consumer maxAge60,correct pairSIM-X/SIM-Y,decimals2. Raw answer12345 means123.45 Y/X. Dependency route: wrappedX→redeemerR→feedF→lenderL→exitPoolE. No real contracts or timestamps.

Wallet-graph-family dependency map, edges explicitly technical dependencies not identity/funding attribution; feed metadata side panel, age100>60, raw answer conversion and failed-redemption branch.

The fixture's freshness failure, decimal conversion and stipulated dependency route.

Actual feed configuration, provider independence, redeemability, audit effectiveness or protocol safety.

• OBSERVED: FIX-P11-L07 gives updateT900 and checkT1000.
• INFERRED: age100 fails the supplied 60-second consumer rule.
• UNKNOWN: actual provider independence and redemption capacity.
• INSUFFICIENT EVIDENCE: oracle updates or an audit guarantee solvency.

• Treating heartbeat as consumer acceptance rule.
• Ignoring pair or decimals.
• Assuming audit covers every dependency.

Compute feed age and normalized answer. Decide acceptance under the supplied consumer policy. Map a redemption outage through the route and name two checks beyond freshness.

Deliver calculations or annotations, claim/source table and limitations. Suggested allocation: study 12 minutes, exercise 8, correction/quiz 10; estimate subject to calibration.

• Verify pair/network/units.
• Compute age against consumer policy.
• Map shared upstream dependencies.
• Preserve audit and oracle limitations.

Oracle assessment combines identity, units, freshness and economic dependencies. Composable mechanisms and audits remain bounded evidence.

• Map oracle and composability dependencies.
• Identify stale-data and local-price limitations.

P11-L08 after correction review.

NONE in the authoritative catalog. The supplied offline fixture/package is sufficient; no paid feature or unverified Production capability is required. Lab/certification metadata denotes downstream associations, not access gates or live awards.

• [ORACLE] Chainlink — Data feeds overview — Aggregation, proxy dependencies and timestamp/deviation/heartbeat limitations. Checked 2026-10-01; locator turn12view3.
• [V2] Uniswap v2 core whitepaper (March 2020) — Reserve ratio, constant-product mechanics and input-fee invariant; version-specific, not a live deployment snapshot. Checked 2026-10-01; locator turn14view0.