> For the complete documentation index, see [llms.txt](https://docs.hatchr.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatchr.fun/developers/verify-a-token.md).

# Verify a Hatchr Token

An address ending in `e99` is not enough. Verify origin from the official factory.

## Verification checklist

1. Confirm the network is Robinhood Chain, chain ID `4663`.
2. Open the [official factory](https://robinhoodchain.blockscout.com/address/0x99bf0f2f7de390225738bb21847086a9cd6826a2).
3. Find the `TokenCreated` event containing the token address.
4. Record the emitted creator, pool and position token ID.
5. Confirm the pool contains the token and official WETH.
6. Confirm the position is registered in the official LP locker.
7. Confirm the token clone delegates to the published implementation.
8. Compare metadata with the URI stored by the token.

## Canonical factory

```
0x99bf0f2f7de390225738bb21847086a9cd6826a2
```

## Why suffix matching fails

CREATE2 address mining is permissionless. Another deployer can create an unrelated address with the same final characters. The `TokenCreated` event binds a token to the official Hatchr factory.

{% hint style="danger" %}
Names, tickers, logos and social accounts can be copied. Contract provenance is the primary identity check.
{% endhint %}


---

# 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://docs.hatchr.fun/developers/verify-a-token.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.