- Storage Proofs: A fusion of inclusion proofs, which confirm data’s presence, and proofs of computation, which validate the execution of a multi-step workflow to attest the validity of one or multiple elements in a large dataset such as the whole Ethereum blockchain or a rollup.
- Block Hash: A unique identifier for a block, summarizing all its contents. It’s crucial for anchoring Storage Proofs to a specific point in blockchain history.
- Block Header: Contains metadata about a block, including important roots (state, receipts, transactions) used in the Storage Proof process.
- Merkle Trees: Data structures used in blockchains to efficiently and securely verify the contents of large data sets.
- Inclusion Proofs: Demonstrate that a specific piece of data is part of a larger data set (like a Merkle tree) without revealing the entire data set.
- Zero-Knowledge Proofs: Allow verification of information without revealing the underlying data, enhancing privacy and efficiency in blockchain systems.
- Mission Control: The production service that serves the Storage Proof API — submit proof requests, track queries, and manage grow orders.
- Satellite: On-chain contracts that store and expose proven blockchain data so other contracts can read verified values safely.
- Historical Block Hash Accumulator: A system that allows smart contracts to access and verify historical block hashes efficiently.
- Cross-Chain Interoperability: The ability for different blockchain networks to communicate and share data securely, a key use case for Storage Proofs.
Getting Started
Key Concepts
Essential concepts for understanding Storage Proofs including block hashes, inclusion proofs, and zero-knowledge verification
Before diving into the details of Storage Proofs, it’s important to understand some key concepts:

