Replace or remove a feed
Change the feed address for an existing subject and topic, or remove a feed registration from the Feeds Directory.
Replace a feed when the subject and topic should stay active but future reads must resolve to a different feed contract. Remove a feed when that subject and topic should stop resolving through the Feeds Directory.
Replacement and removal change only the directory registration. The old feed contract and historical values remain unchanged. DALP does not prove whether an external market data source is economically correct.
Prerequisites
- Feeds manager role (
feedsManager) assigned on the System Access Manager - An active feed registration for the subject and topic
- For replacement: the new scalar feed contract address and a short description for the new registration
- Wallet verification configured for the transaction confirmation step
Before you confirm
Replacement and removal are operational changes to the directory that other DALP surfaces can read. Before you submit either operation:
- Confirm the subject and topic identify the exact feed registration you intend to change.
- For replacement, check that the new address is the feed contract consumers should read next, then enter a description that identifies the replacement in the directory.
- For removal, confirm that consumers can tolerate a missing feed for that subject and topic.
- Keep the old feed contract address if you need to investigate historical activity after the mapping changes.
Directory changes affect consumers
Replacing a feed changes which contract is resolved for the subject and topic. Removing a feed makes that subject and topic resolve to no feed. Check downstream price, reporting, and smart contract consumers before confirming either operation.
Replace a feed
Open the feed detail menu
Go to Platform Settings > Data Feeds. Open the feed detail page, then open the menu and choose Replace feed.
Enter the replacement address
Enter the new scalar feed contract address and a description for the updated registration. DALP submits a replaceFeed transaction for the same subject and topic. The transaction points the directory registration at the new address.
The replacement address must be a compatible scalar feed for the same kind of data. Use a feed contract that exposes the expected feed interface and the same decimal precision as the current feed.
Review the before-and-after summary
Review the topic, subject, current feed address, and new feed address. Confirm only when the new feed is the contract that should serve future reads for this subject and topic.
Confirm the transaction
Submit the replacement and complete wallet verification. After the transaction confirms, the Data Feeds list refreshes and future directory resolution uses the replacement feed.
A Chainlink-compatible adapter registered for the same subject and topic resolves through the directory. After replacement, adapter consumers read the new feed address instead of the old one.
Remove a feed
Open the remove control
Go to Platform Settings > Data Feeds. Open the feed detail page, then open the menu and choose Remove feed.
Review the warning
The confirmation dialog shows the feed address and explains that DALP will remove the registration. Select the checkbox only when the subject and topic should no longer resolve to a feed.
Confirm wallet verification
Submit the removal and complete wallet verification. After the transaction confirms, DALP returns you to the Data Feeds list and refreshes feed data.
Removing a registration does not delete the old feed contract. Removal clears the directory mapping for the subject and topic. Discovery flows and adapter consumers must handle the missing feed state.
What changes after replacement or removal
| Operation | Directory result | Existing feed contract | Consumer impact |
|---|---|---|---|
| Replace feed | The subject and topic resolve to the new feed address | The old contract remains deployed with its historical state | Future reads through the directory or adapter use the replacement feed |
| Remove feed | The subject and topic no longer resolve to a feed | The old contract remains deployed with its historical state | Consumers that rely on directory resolution must handle a missing feed |
Troubleshooting
| Issue | What to check |
|---|---|
| Replace or remove control is not visible | Confirm your user has the Feeds manager role. |
| Replacement address is rejected | Check that the address is a compatible feed contract on the target network and uses the same decimal precision as the current feed. |
| Replacement cannot continue | Enter both a valid new feed address and a description for the replacement registration. |
| Transaction fails during confirmation | Check wallet verification, gas balance, and whether the subject and topic still resolve to the feed being changed. |
| Consumers still show old data | Wait for the transaction and indexer to complete, then refresh the consumer view. |
The API returns a transaction result for synchronous confirmations, or an asynchronous status response when the request is accepted for later completion. The page refreshes after confirmation and indexing, so a short delay before downstream views show the new directory state is normal.
Related guides
- Data feeds overview - Roles, scopes, and operating boundaries
- Create a feed - Register issuer-signed or Chainlink-compatible feeds
- Publish a feed update - Submit values to issuer-signed feeds
- Read data feeds - Resolve feeds and read latest or historical values through the API