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
  • Relayer Component in Detail
  • Relayer & gRPC

Was this helpful?

Edit on GitHub
  1. Architecture
  2. Components

Relayer

StreamingFast Firehose relayer component

Relayer Component in Detail

The Relayer component is responsible for providing executed block data to other Firehose components.

The Relayer component feeds from all available Reader nodes to get a comprehensive view of all possible forks.

The Relayer "fans out", or relays, block information to the other Firehose components.

Relayer & gRPC

The Relayer component serves its block data through the streaming gRPC interface BlockStream::Blocks. This is the same interface that the Reader component exposes to the Relayer component. Read more about the BlockStream::Blocks interface in its GitHub repository.

PreviousMergerNextgRPC Server

Last updated 2 years ago

Was this helpful?