Architecture Overview

Below is a simplified picture of how Facet components fit together, followed by a more detailed Mermaid diagram.

The simplified flow:

• L1: Users submit Facet payloads to inbox EOA 0xface7 (see Sending Transactions). Rollup.sol (ZK Fault Proofs) lives on L1.

• L2: facet-node derives Facet blocks from L1 (see Chain State Derivation) and sends them to facet-geth which holds state.

• Proposer/Challenger: read from facet-geth and interact with Rollup.sol (with ZK proofs) (see Proposing and Challenging).

• Bridges/Apps on L1: read canonical roots from Rollup.sol to verify withdrawals (see Building Bridges).

See also

• Immutable Sequencing → Sending Transactions

• Reference → Chain State Derivation

• Proof System & Bridging → ZK Fault Proofs

• Proof System & Bridging → Building Bridges