> For the complete documentation index, see [llms.txt](https://nytshift.gitbook.io/nytshift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nytshift.gitbook.io/nytshift-docs/market-data-and-providers/registry-mismatch.md).

# Robinhood Chain registry mismatch

1. Treat any token/feed mismatch, duplicate feed or unknown contract as unavailable. Symbol/name similarity is not evidence of identity.
2. Compare the checked-in canonical token registry with Robinhood Chain's official contracts page and the checked-in feed snapshot with Chainlink's Robinhood reference-data directory.
3. Prepare an explicit source change containing the new token/feed address, heartbeat, registry version and upstream source timestamp.
4. Require review of the manifest diff and deterministic registry tests before deployment.
5. Re-run provider reads against chain ID `4663`; verify bytecode exists and feed decimals/round data decode correctly.
6. Deploy normally. There is no runtime or browser endpoint for injecting registry entries.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nytshift.gitbook.io/nytshift-docs/market-data-and-providers/registry-mismatch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.