LogoLogo
  • 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
    • Injective
      • Single-Machine Deployment
    • NEAR
      • Single-Machine Deployment
    • Solana
      • 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

Was this helpful?

Edit on GitHub
  1. Architecture
  2. Components

Firehose-enabled Node

StreamingFast Firehose Firehose-enabled node component

PreviousComponentsNextReader

Last updated 2 years ago

Was this helpful?

Firehose-enabled Node in Detail

The Firehose-enabled Blockchain Node is a third-party blockchain node client, such as Ethereum, instrumented under StreamingFast practices to output data that will be read by the Firehose Reader component.

Note: The component will consume the data produced by the Firehose-enabled Blockchain Node.

The Firehose-enabled Blockchain Node runs in tandem with the component. The two components are connected either through a UNIX pipe using stdout, or by having the component's process execute and fork the blockchain client. This is accomplished using the node-manager software included in Firehose.

Blockchain nodes used in this capacity require:

  • very few features,

  • no archive mode capability,

  • no JSON-RPC service,

  • and no indexed data will be queried.

The is responsible for executing all transactions in an order respecting the consensus protocol of the blockchain.

Reader
Reader
Reader
Firehose-enabled Blockchain Node