Firehose
  • Firehose
  • Introduction
    • Firehose Overview
    • Prerequisites
  • Architecture
    • Components
      • Firehose-enabled Node
      • Reader
      • Merger
      • Relayer
      • gRPC Server
      • High Availability
    • Data Flow
    • Data Storage
  • Firehose Setup
    • Overview
    • Ethereum
      • Installation
      • Single-Machine Deployment
      • Reprocessing history
      • Synchronization
    • Cosmos
      • Single-Machine Deployment
    • NEAR
      • Single-Machine Deployment
    • System Requirements
  • Community Integrations
    • Starknet
      • Networks and nodes
      • Local deployment with Docker
      • Local deployment without Docker
  • Integrate New Chains
    • Benefits
    • Integration overview
    • Design Principles
    • Firehose Acme
  • References
    • Supported Protocols
    • Naming Conventions
    • Schemas
    • Indexing
    • FAQ
  • Release Notes
    • Change logs
      • Nov 8th 2023 Polygon Update
Powered by GitBook
On this page
  1. Community Integrations

Starknet

Firehose for Starknet

PreviousSystem RequirementsNextNetworks and nodes

Last updated 1 year ago

Setting up Firehose for Starknet shares a very similar process as setups for other chains. This section provides resources and instructions for successfully running it.

Tip: If you want to have a quick peek at what a complete stack including graph-node for subgraph indexing looks like, look no further than the , which features an end-to-end guide for getting everything up and running in under 5 minutes. This section here focuses on Firehose itself only.

The first step for running Starknet Firehose is to decide on the network to run on and the node to use. More details can be found on the page.

From there, depending on whether you want to use Docker or not, there are 2 different routes:

  • : Everything you need to run a successful Firehose is in multi-arch (AMD64 and ARM64) Docker images. Deploying with Docker is extremely easy.

  • : This page guides you through setting up your machine for running the stack without using Docker.

Tip: If you run into issues trying to run the stack without Docker, consider trying with the Docker approach to see if the issues persist, as the Docker setup has way fewer moving parts that can lead to failures. This could be helpful in diagnosing the issues even if you eventually still choose to deploy without Docker.

quickstart tutorial
Networks and nodes
Local deployment with Docker
Local deployment without Docker