Dependency Graph
Visual Graph
Dependency Table
| Component | Depends on | Required by |
|---|---|---|
| L1/L2 Node | Component Framework | Erigon Archive, Map-Reduce Framework, Proof Integration, EIP-8141, Interop Bridge, QMTree |
| Component Framework | — | L1/L2 Node |
| Modular TX Pipeline | — (foundational) | EIP-8141, Interop Bridge, Shutter, Lucid |
| EIP-8141 Frame Txns | Modular TX Pipeline, L1/L2 Node | Interop Bridge (Phase 3+) |
| Erigon Archive | L1/L2 Node (Storage + SharedDomains flush path) | Sparse Snapshots (detached mode) |
| Map-Reduce Framework | L1/L2 Node (Storage + Execution event bus) | QMTree Commitment (backfill), Modular TX Pipeline (per-type tracing) |
| Proof Integration | L1/L2 Node (Consensus component, RollupDriver) | — |
| Interop Bridge | L1/L2 Node (Phases 1–3), Modular TX Pipeline, EIP-8141 | — |
| QMTree Commitment | L1/L2 Node (Storage), Map-Reduce Framework (backfill) | — |
| Sparse Snapshots | Erigon Archive (detached mode concept) | — |
Critical Paths
For EIP-8141:
Modular TX Pipeline → EIP-8141
For Interop Bridge (full):
L1/L2 Node Phase 1 → Bridge Phase 1 → Bridge Phase 2
Modular TX Pipeline → EIP-8141 → Bridge Phase 3 → Bridge Phase 4
L1/L2 Node Phase 2 → Bridge Phase 5 (P2P)
L1/L2 Node Phase 3 + Bridge Phase 4 → Bridge Phase 6 → Bridge Phase 7
For QMTree backfill:
L1/L2 Node (Storage) → Map-Reduce Framework Phase 0 ✓ → QMTree backfill
For Sparse Snapshots production:
Erigon Archive (Detached mode) + Sparse Snapshots caching layer
What Can Start Now
These components have no blocking dependencies and can be worked on independently:
| Component | Why it can start |
|---|---|
| Modular TX Pipeline | No dependencies — foundational refactor |
| Erigon Archive Phase 1–2 | Only requires SharedDomains refactor (internal) |
| Map-Reduce Framework Phase 1–2 | Phase 0 done; next phases are additive |
| Component Framework integration Wave 1 | Flag consolidation only — no behavioral change |
| QMTree (feature work) | Branch exists; active on Hoodi testnet |