How celo-org/optimism works
This repository is a collection of OP Stack clients, services, and operator tools rather than one application. A representative chain workflow derives L2 payload attributes from rollup data, coordinates execution through an engine API, and submits batches to L1; fault-proof challenges and deployment are distinct operational workflows. The graph preserves these stages and major documented components, plus shared engine-facing and integration layers. Some subsystems are represented by directory paths because their source was not sampled; relationships are limited to visible imports or README descriptions.
Main entry points: op-node Rollup client · pipeline.go Derivation pipeline · engine_client.go Engine RPC client · engine_controller.go Engine controller
Components 24
Rollup and execution
- Rollup client
op-node - Derivation pipeline
op-node/rollup/derive/pipeline.go - Payload attributes
op-node/rollup/attributes/engine_consolidate.go - Engine controller
op-node/rollup/engine/engine_controller.go - Engine RPC client
op-service/sources/engine_client.go - Execution client
rust/op-reth/crates/node/src/engine.rs - Rust derivation stages
rust/kona/crates/protocol/derive/src/stages
Batch submission
- Channel manager
op-batcher/batcher/channel_manager.go - Submission throttler
op-batcher/batcher/throttler/controller.go - Batcher service
op-batcher/cmd/main.go
Fault proofs
- Challenge agent
op-challenger - Challenger CLI
op-challenger/cmd/main.go - MIPS fault VM
cannon/mipsevm - Rust proof pipeline
rust/kona/crates/proof/driver/src/pipeline.rs
Deployment and operations
- Contract deployer
op-deployer/pkg/deployer - Chain operations
op-chain-ops/cmd/check-lagoon/main.go - Devnet launcher
op-up/main.go
Integration and shared tools
- Multi-chain host
op-supernode/supernode/chain_container/engine_controller/engine_controller.go - Interop log ingester
op-interop-filter/filter/logsdb_chain_ingester.go - E2E engine harness
op-e2e/actions/helpers/l2_engine.go - Test engine API
op-e2e/actions/helpers/engineapi/l2_engine_api.go - Engine utility
op-wheel/engine/engine.go
Other components
- Operator
- Chain user
Connections 19
- Chain user → Rollup client: uses chain
README.md - Rollup client → Derivation pipeline: derives blocks
op-node/cmd/main.go - Derivation pipeline → Payload attributes: builds attributes
op-node/rollup/derive/pipeline.go - Engine controller → Derivation pipeline: uses derivation
op-node/rollup/engine/engine_controller.go - Engine controller → Engine RPC client: creates client
op-service/sources/engine_client.go - Engine RPC client → Execution client: sends engine calls
op-service/sources/engine_client.go - Batcher service → Channel manager: runs batching
README.md - Channel manager → Submission throttler: throttles submissions
op-batcher/batcher/channel_manager.go - Operator → Challenger CLI: starts agent
op-challenger/cmd/main.go - Challenger CLI → Challenge agent: starts service
op-challenger/cmd/main.go - Challenge agent → MIPS fault VM: uses fault VM
README.md - Operator → Contract deployer: deploys contracts
README.md - Operator → Chain operations: runs operations
op-chain-ops/cmd/check-lagoon/main.go - Operator → Devnet launcher: launches devnet
op-up/main.go - Multi-chain host → Engine RPC client: constructs client
op-supernode/supernode/chain_container/engine_controller/engine_controller.go - Interop log ingester → Rollup client: imports rollup types
op-interop-filter/filter/logsdb_chain_ingester.go - E2E engine harness → Test engine API: registers API
op-e2e/actions/helpers/l2_engine.go - Rust derivation stages → Rust proof pipeline: derives proof inputs
- Operator → Engine utility: uses engine tools
README.md