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
  1. Protocol Design

Architecture

PreviousIntegrity VerifierNextSmart Contracts

Last updated 1 year ago

Herodotus is composed of both on-chain and off-chain components. The key components are:

Smart Contracts

These contracts relay block hashes across Ethereum layers and verify storage proofs, among other tasks. Learn more .

Cairo Programs: Proven off-chain.

We use off-chain Cairo for intensive tasks, like expanding our accumulators with many proven block headers.

Circuits: Proven off-chain.

We utilize circuits to efficiently verify state proofs from specific zk-rollups. Currently, we haven't implemented these in production, but they'll be available in the future.

here