Specify the input contract
Write down the accepted feed identifier, expected meaning, numerical representation, and required timestamps. A feed name alone does not tell an application how to interpret its output. Check the actual integration and deployed configuration.
Chainlink's Data Feeds API reference exposes decimal information and update timestamps for its documented interface. Those fields illustrate why value and metadata should be reviewed together. In a hypothetical integration, accepting the right integer with the wrong scale would defeat an otherwise correct calculation. The application should make the intended representation explicit.
Define rejection and recovery behavior
Give stale, unavailable, malformed, and inconsistent inputs separate outcomes. Specify whether the affected operation stops, waits for another update, or uses an explicitly documented fallback. A fallback needs its own acceptance criteria and a visible indication that the normal path changed.
Consider a report with an observation time later than the application's reference time. Decide how that condition is handled before it occurs. The smart contract checks article explores validation questions that connect input identity, timing, and the consequence of accepting an unsuitable observation.
Connect configuration to user authorization
Identify who can change the feed address, limits, fallback rules, or contract implementation, where such powers exist. A review should describe the configuration actually governing the operation and how a material change becomes visible.
Then compare the transaction preview with the enforced limits. A reference price displayed on the page should not stand in for a minimum received amount or a maximum permitted spend. Ask what happens if relevant state changes before execution. Continue with Oracle Wallet foundations to place these application rules beside source evaluation and signing authority.
