# Overview

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](/integration/platform/l1-l2-node.md) — running Ethereum L1 and any rollup type inside a single binary
* [Technical Design](/integration/platform/l1-l2-node-design.md) — RollupDriver interface, staged sync pipeline, chain config extension
* [Component Framework](/integration/platform/componentization.md) — lifecycle-managed components with typed providers and dependency ordering

**Components** — individually composable subsystems that extend or replace Erigon internals:

* [Modular Transaction Pipeline](/integration/components/modular-tx-pipeline.md) — registry-based transaction type handling
* [EIP-8141 Frame Transactions](/integration/components/eip-8141.md) — protocol-native account abstraction
* [Erigon Archive](/integration/components/erigon-archive.md) — decoupled block execution and storage
* [Map-Reduce Framework](/integration/components/map-reduce.md) — parallel historic block replay
* [Proof Integration](/integration/components/proof-integration.md) — pluggable prover and verifier backends
* [Interop Bridge](/integration/components/interop-bridge.md) — cross-L2 bridge implementing the Ethereum Interop Layer protocol

**Proofs of Concept** — experimental subsystems validated independently:

* [Sparse Snapshots](/integration/proofs-of-concept/sparse-snapshots.md) — on-demand full-history node bootstrap from BitTorrent
* [QMTree Commitment](/integration/proofs-of-concept/qmtree-commitment.md) — 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](/integration/reference/dependency-graph.md). Build status is in [Reference → Component Status](/integration/reference/status.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cocoon.erigon.tech/integration/getting-started/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.