# Chain Specific

This section contains chain-specific configuration guides for Firehose. Each guide covers the Reader Node configuration required to extract blockchain data for that particular chain.

Before reading these guides, ensure you understand the general deployment concepts from:

* [Single Machine Deployment](/firehose/overview/single-machine-deployment.md) - For development or small-scale deployments
* [Distributed Deployment](/firehose/overview/distributed-deployment.md) - For production deployments

## Supported Chains

### EVM Chains

Ethereum and EVM-compatible chains use `fireeth` and share similar configuration patterns:

| Chain                                                          | Type            | Notes                      |
| -------------------------------------------------------------- | --------------- | -------------------------- |
| [Ethereum](/firehose/overview/chains/ethereum.md)              | Native Firehose | Mainnet, Sepolia, Hoodi    |
| [Arbitrum](/firehose/overview/chains/ethereum/arbitrum.md)     | Native Firehose | Requires L1 connection     |
| [Base](/firehose/overview/chains/ethereum/base.md)             | Native Firehose | OP Stack, requires OP Node |
| [BNB Smart Chain](/firehose/overview/chains/ethereum/bsc.md)   | Native Firehose | BSC Geth fork              |
| [Katana](/firehose/overview/chains/ethereum/katana.md)         | Native Firehose | OP Stack                   |
| [Optimism](/firehose/overview/chains/ethereum/optimism.md)     | Native Firehose | OP Stack, requires OP Node |
| [Polygon](/firehose/overview/chains/ethereum/polygon.md)       | Native Firehose | Bor client                 |
| [Unichain](/firehose/overview/chains/ethereum/unichain.md)     | Native Firehose | OP Stack                   |
| [Worldchain](/firehose/overview/chains/ethereum/worldchain.md) | Native Firehose | OP Stack                   |
| [Avalanche](/firehose/overview/chains/avalanche.md)            | RPC Poller      | C-Chain via RPC            |
| [Sei](/firehose/overview/chains/sei.md)                        | Native Firehose | Cosmos SDK + EVM           |

### Non-EVM Chains

These chains use `firecore` with chain-specific binaries:

| Chain                                               | Type            | Notes                    |
| --------------------------------------------------- | --------------- | ------------------------ |
| [Injective](/firehose/overview/chains/injective.md) | RPC Poller      | Cosmos SDK chain         |
| [NEAR](/firehose/overview/chains/near.md)           | Native Firehose | NEAR Protocol            |
| [Solana](/firehose/overview/chains/solana.md)       | Geyser Plugin   | Solana validator plugin  |
| [Starknet](/firehose/overview/chains/starknet.md)   | RPC Poller      | Requires Ethereum L1 RPC |
| [Stellar](/firehose/overview/chains/stellar.md)     | RPC Poller      | Soroban RPC              |
| [Tron](/firehose/overview/chains/tron.md)           | RPC Poller      | Native and EVM formats   |

## Integration Types

### Native Firehose

Chains with native Firehose instrumentation have a patched blockchain client that outputs block data in Firehose format. This provides the most complete data extraction.

### RPC Poller

For chains without native instrumentation, an RPC poller fetches blocks from standard RPC endpoints. You can use your own node or an RPC provider.

### Geyser Plugin

Solana uses a Geyser plugin that hooks into the validator to extract block data.


---

# Agent Instructions: 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:

```
GET https://firehose.streamingfast.io/firehose/overview/chains.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.