> For the complete documentation index, see [llms.txt](https://firehose.streamingfast.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://firehose.streamingfast.io/firehose/overview/chains/avalanche.md).

# Avalanche

This page covers Reader Node configuration specific to Avalanche C-Chain. For general Firehose architecture and deployment, see the [Single Machine Deployment](/firehose/overview/single-machine-deployment.md) or [Distributed Deployment](/firehose/overview/distributed-deployment.md) guides.

{% hint style="warning" %}
Firehose for Avalanche uses an RPC poller approach. You can either run your own Avalanche node or use an RPC provider. For node setup, refer to the [official Avalanche documentation](https://docs.avax.network/).
{% endhint %}

## Docker Image

```
ghcr.io/streamingfast/go-ethereum:geth-<version>-fh3.0
```

[View available versions on GitHub Packages](https://github.com/streamingfast/go-ethereum/pkgs/container/go-ethereum)

The image contains the `fireeth` binary with the RPC poller.

## Binary & Releases

| Component | Repository                                                              | Binary    |
| --------- | ----------------------------------------------------------------------- | --------- |
| Firehose  | [firehose-ethereum](https://github.com/streamingfast/firehose-ethereum) | `fireeth` |

Download releases from the [GitHub releases page](https://github.com/streamingfast/firehose-ethereum/releases).

## Networks

| Network           | Chain Name          |
| ----------------- | ------------------- |
| Avalanche C-Chain | `avalanche-mainnet` |

## Architecture

Firehose for Avalanche uses an **RPC poller** approach. The poller fetches blocks from Avalanche C-Chain RPC endpoints (which are EVM-compatible) and converts them to Firehose format.

```
┌──────────────────┐     RPC      ┌──────────────────┐     stdout    ┌──────────────┐
│  Avalanche RPC   │◄────────────│     fireeth      │──────────────►│  Reader Node │
│    Endpoint      │              │     poller       │               │  (Firehose)  │
└──────────────────┘              └──────────────────┘               └──────────────┘
```

## Reader Node Configuration

### Avalanche C-Chain Mainnet

```bash
fireeth start reader-node <apps> \
  --advertise-chain-name="avalanche-mainnet" \
  --common-first-streamable-block=<start-block> \
  --reader-node-path="fireeth" \
  --reader-node-arguments="tools poller optimism <rpc-endpoint> {first-streamable-block}" \
  <other_flags...>
```

## Key Poller Flags

| Flag                       | Description                                                 |
| -------------------------- | ----------------------------------------------------------- |
| `tools poller optimism`    | Subcommand to run the EVM RPC poller                        |
| `<rpc-endpoint>`           | Avalanche C-Chain RPC endpoint URL                          |
| `{first-streamable-block}` | Variable substituted from `--common-first-streamable-block` |

## Resources

* [Avalanche Documentation](https://docs.avax.network/)
* [Avalanche C-Chain RPC](https://docs.avax.network/apis/avalanchego/apis/c-chain)
* [firehose-ethereum GitHub](https://github.com/streamingfast/firehose-ethereum)


---

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

```
GET https://firehose.streamingfast.io/firehose/overview/chains/avalanche.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.