Freshness and invalid data
Refresh a price when your application needs it, with the validity and freshness information to decide how to use it.
A stored price can be displayed as is; judge its age and validity against your own policy. Where off-chain prices come from: provenance.
Using the feed's status
| Condition | Integration guidance |
|---|---|
| Wrong feed or mismatched accounts | Resolve the intended feed and matching accounts before using the price. |
| Inactive or invalid state | Wait for a valid, active feed before using it as a price reference. |
| Expired validity window or unacceptable age | Use the supported refresh path, or defer the action. |
| Insufficient sources or liquidity | Keep the application's source and liquidity criteria in place. |
| RPC or refresh failure | Show an unavailable state and follow a defined retry/recovery policy. |
Composite feeds inherit dependencies
A composite draws on its component prices and any quote conversions. Mimir checks these inputs against the feed's validity rules. Input timestamps describe the age of the component data; the composite's calculation time records when that data was combined.
Price data and application policy
Mimir exposes the price's sources and validity information. Applications combine that information with their own requirements for liquidity, exposure and the assets they support. For tokenized assets, the issuer's terms also inform those choices.
Next: manipulation safeguards.