> For the complete documentation index, see [llms.txt](https://docs.digitaldon.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitaldon.net/getting-started/chains.md).

# Supported chains

## Always on

| Chain        | Search | Chart & score | Holder analysis      |
| ------------ | ------ | ------------- | -------------------- |
| **Solana**   | ✅      | ✅             | ✅ full (owner-level) |
| **Ethereum** | ✅      | ✅             | ✅ full               |
| **Base**     | ✅      | ✅             | ✅ full               |

## Also available

| Chain               | Notes                                                                                                                     |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **BSC**             | On by default. Chart and score are full-strength; holder analysis has thinner evidence to work with than the three above. |
| **Robinhood Chain** | Opt-in. Newer chain — core wallet clustering works, some launch signals aren't available.                                 |

Which chains are live is an instance-level setting. On the public bot, Solana, Ethereum, Base and BSC are on.

## When a ticker exists on several chains

Searching `PEPE` will match tokens on more than one chain. Rather than picking for you, the bot shows a disambiguation picker with the chain, price and liquidity of each match, and you tap the one you meant. The Web Analyzer does the same thing with a list of cards.

Contract addresses skip this entirely — a Solana mint or an `0x` address resolves directly. (An `0x` address *can* exist on more than one EVM chain, so the chain is taken from whichever pair actually resolves, and results are kept separate per chain so Base and Ethereum never bleed into each other.)

## What "supported" actually needs

For a token to be analysable at all, three things have to line up:

1. **The pair is discoverable** — that's where price, liquidity, FDV, market cap and the 24h buy/sell split come from.
2. **Chart history exists for the pool** — no candles, no technical analysis. Very new or very thin pools often have none.
3. **There's enough of it** — below a small floor of usable candles there's nothing honest to compute.

If (2) or (3) fail on a token that's only a few days old, you don't get an error — you get a [fresh-launch card](/how-the-analysis-works/onchain.md#fresh-launch-cards) built from chain data instead. If the token is older than that, missing chart data means the source failed, and the card says so rather than pretending the token is new.


---

# 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.digitaldon.net/getting-started/chains.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.