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

# Supported Chains

## Chain matrix

Eight chains are recognized by the URL parser. The depth of feature support varies by chain:

| Chain    | Info | Holders | KOLs | Lore | Summary | Feed    | Audit |
| -------- | ---- | ------- | ---- | ---- | ------- | ------- | ----- |
| Solana   | ✓    | ✓       | ✓    | ✓    | ✓       | ✓       | -     |
| Ethereum | ✓    | ✓       | ✓    | ✓    | ✓       | ✓       | ✓     |
| Base     | ✓    | ✓       | ✓    | ✓    | ✓       | ✓       | ✓     |
| BSC      | ✓    | ✓       | ✓    | ✓    | ✓       | ✓       | ✓     |
| Blast    | -    | -       | -    | -    | partial | partial | -     |
| Abstract | -    | -       | -    | -    | partial | partial | -     |
| Monad    | -    | -       | -    | -    | partial | partial | -     |
| Tron     | -    | -       | -    | -    | -       | -       | -     |

The four mature chains have full feature parity except for audit (which is EVM-only, so Solana sits this out). Audit covers the three mature EVM chains. Newer chains (Blast, Abstract, Monad) are recognized by the URL parser and may receive partial responses from the AI and feed services as upstream coverage develops; they do not yet have indexer-backed info, holders, KOLs, or lore. Tron is recognized but currently has no backend coverage.

## Why the depth varies

Each chain requires an indexer with full transaction history and event decoding for that chain's DEX ecosystem, wallet-graph coverage (named wallets active on that chain), and social-ingestion coverage (signal that maps to that chain's tokens). The four mature chains have established trader populations and mature indexer infrastructure. The emerging chains have one or more gaps we are actively closing.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://thesium.gitbook.io/thesium-docs/coverage/supported-chains.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.