Herodotus Docs
Home
  • Introduction
  • FAQ
  • developers
    • Storage Proofs
      • Workflow
      • Workflow Examples
      • Accessing Block Hash
    • Storage Proof API
      • Interactive Docs
      • Step by step example
    • Turbo
      • Supported Networks
      • Turbo zksync demo
    • Data Processor
      • Why use HDP?
      • Getting Started
      • HDP Jargon
        • What is a Data Lake?
        • What is a Module?
        • Cairo1/Cairo0 Interoperability
      • Architecture
      • Additional Resources
    • Data Processor API
      • Program Registry API
      • Interactive Docs
    • Data Structure Indexer API
      • Interactive Docs
    • Supported Networks
    • Contract Addresses
    • API Status
  • Scaling Solutions
    • Integrity Verifier
  • Protocol Design
    • Architecture
      • Smart Contracts
      • OP Stack
    • Historical Block Hash Accumulator
      • Merkle Mountain Ranges
      • Initial Accumulation Event
    • Timestamp to Block Mapper
      • Edge Cases
  • Security
    • Audits
  • GitHub
  • Twitter
  • LinkedIn
  • Telegram
  • Media Kit
Powered by GitBook
On this page
  • Supported Networks
  • Storage Proof API
  • Turbo
  • Data Processor
  1. developers

Supported Networks

Support for new blockchains is added by developing new “data connections.” We define “data connections” as support for reading the state of two distinct Ethereum blockchains (L1s and/or L2s). Data connections can be one-directional or bi-directional.

For example, reading Ethereum Goerli from zkSync Era Goerli is a one-directional data connection as it enables reading arbitrary Ethereum Goerli on-chain data on zkSync Era Goerli. Please note that this is a one-directional connection, as reading zkSync Era Goerli data from Ethereum Goerli is not supported at this time.

Our mission is to enable bi-directional data connections between all Ethereum ecosystem blockchains.

The origin chain is the source from which the on-chain data is retrieved. The destination chain is where we want to access origin chain data from.

Supported Networks

Storage Proof API

Origin
Destination

Ethereum

Starknet

Ethereum Goerli*

Starknet Goerli*

Ethereum Goerli*

zkSync Era Goerli*

Ethereum Goerli*

Optimism Goerli*

Turbo

Origin
Destination

Ethereum Goerli*

zkSync Era Goerli*

Data Processor

Origin
Destination

Ethereum Goerli*

Ethereum Goerli*

Ethereum Goerli*

Starknet Goerli*

*Test network

PreviousData Structure Indexer APINextContract Addresses

Last updated 7 months ago