Overview
Erigon client integration — modular platform components for building ZK-enabled chains
This space covers the technical integration layer between Cocoon and the Erigon node — the modular platform components that operators, contributors, and integrators work with directly.
It is organized into three areas:
Platform — the foundational node architecture for running L1 and rollup chains:
L1/L2 Node — running Ethereum L1 and any rollup type inside a single binary
Technical Design — RollupDriver interface, staged sync pipeline, chain config extension
Component Framework — lifecycle-managed components with typed providers and dependency ordering
Components — individually composable subsystems that extend or replace Erigon internals:
Modular Transaction Pipeline — registry-based transaction type handling
EIP-8141 Frame Transactions — protocol-native account abstraction
Erigon Archive — decoupled block execution and storage
Map-Reduce Framework — parallel historic block replay
Proof Integration — pluggable prover and verifier backends
Interop Bridge — cross-L2 bridge implementing the Ethereum Interop Layer protocol
Proofs of Concept — experimental subsystems validated independently:
Sparse Snapshots — on-demand full-history node bootstrap from BitTorrent
QMTree Commitment — append-only Merkle tree for proof-of-execution
How It Fits Together
The L1/L2 Node is the platform foundation — all other components depend on its Storage, Execution, or Consensus sub-components. The Modular Transaction Pipeline is foundational with no upstream dependencies but required by EIP-8141 and the Interop Bridge. The Map-Reduce Framework and Erigon Archive build on the Node's Storage and Execution components. The two PoCs validate subsystems independently.
The full dependency graph is in Reference → Dependency Graph. Build status is in Reference → Component Status.
Last updated