Organisation data feeds
Register and maintain trusted on-chain data feeds for subjects and topics.
Data feeds registers the trusted on-chain values the organisation's tokens read by subject and topic. A published value and its staleness window here are the same data a token's Feeds tab shows and the same window the on-chain price resolver checks before it accepts a value.
Reach for this page when a token needs a trusted value, a price or another on-chain reference figure, that the platform does not already supply. A token's compliance rules, ownership, and transaction history live elsewhere; this page only feeds the values a token reads.
Creating, publishing, replacing, or removing a feed is one of the operations the organisation's Audit trail records, alongside your name and role at the time, so you can identify the account that submitted the change.
A price resolver starts with a never-expires global window when the account that creates it holds the Feeds Manager role, so no value is rejected for age until an operator sets a finite window or a per-feed override. Otherwise, and for any resolver with no observed global-window event, the on-chain default of one day applies. Set the staleness window to the maximum age your operation accepts, or choose never expires for a deployment-wide default. A shorter window requires more frequent publication. A longer window permits older values and must still meet the asset's pricing requirements. A per-feed override can be set to never expire when that feed has no expiry requirement, or left to inherit the global window. Note too that a token's own governance holder can set that token's feed staleness without needing the Feeds Manager role; only the platform-wide global staleness setting requires it.
A stable adapter gives consumers a fixed address for directory reads. Replacing a feed, covered below, swaps the address the directory resolves for that subject and topic to a new feed contract, so an integration that stores the old feed address continues to read the old contract. Creating an adapter deploys a small, permanent contract that speaks the AggregatorV3 interface most DeFi tooling already expects from a Chainlink feed, and that looks up the current feed through the directory on every read. An integration hard-codes the adapter's address once, and a replacement preserves that address. Check that the new feed still provides the data and precision the consumer expects. A feed already sourced from Chainlink usually skips this: its address is already the stable, canonical one DeFi tooling expects, so wrapping it in another adapter adds indirection without adding stability.
The integration hard-codes the adapter's fixed address once; the directory resolves it to whichever feed is current, so replacing the underlying feed never breaks the integration's stored address.
Steps
Open Data feeds
Open Organisation settings, then Data feeds. If you land on a page-not-found result, ask an administrator to check your Feeds Manager role on the selected network.
Screen equivalent: the table shows each feed's topic, scope, source, latest value, update time, and status.
Create or maintain a feed
Select Create feed to register one, or open a row to publish, replace, remove, or create a stable adapter. Use Global staleness to set the default validity window, or set a per-feed window on an individual row.
An issuer-signed feed created here keeps only its latest round on-chain and accepts only values greater than zero. You cannot configure it to keep bounded or full on-chain history, or use it for a value that can be zero or negative, such as an interest rate or an exchange-rate movement. The indexed API can still serve past accepted observations. An external feed is an existing contract registered in the directory; its own contract determines its value and history rules.
Troubleshooting
Data feeds not available
This system version has no feeds directory. A System Manager must update the system, from System updates, before
feeds can be registered.
A published value is rejected downstream
Check the staleness window. The on-chain price resolver only accepts a value inside the window you set; a value older than that window fails even though the publish itself succeeded here.
Mints keep failing even though the feed looks healthy
Compare the observation time with the permitted age and check the publisher. Publish a fresh value when the current one is stale. Change the window only if the asset's pricing requirements permit older values; a failed mint does not by itself justify accepting stale data.
Replacing a feed instead of creating a new one
Replace keeps the existing directory entry and its downstream references, only swapping the underlying value source, so directory consumers resolve the replacement contract. Check its units, decimals, and topic before switching. Create a new feed instead when the change is not a swap of source but a new subject or topic; replacing an unrelated feed just to reuse its address risks pricing consumers against the wrong figure.