Gate Layer × GateChain: Technical Architecture
High-Level Architecture
The diagram below illustrates the high-level technical architecture of Gate Layer, covering the complete flow from user interaction and L2 execution to L1 settlement and data availability. It clearly depicts how core components like the Sequencer, Batcher, and Proposer work in concert with the Rollup contracts and Blob storage on GateChain to ensure the system's security, efficiency, and scalability.
Key Points of the Diagram
- L1/L2 layering: GateChain (L1) provides settlement and DA; Gate Layer (L2) handles execution and fast confirmations.
- User path: Users interact via RPC Nodes (
gatelayer-node + geth) to submit transactions and query data; deposits can be submitted directly to L1. - Execution stack: Sequencers use
gatelayer-nodewith the Engine API to drivegeth(EVM), producing L2 blocks under EIP‑1559 fee model. - Internal roles: The
batcheraggregates transaction data and writes batches/assertions to L1 Blobs (EIP‑4844); theproposercomputes and submits output roots (state/output roots) to L1 contracts. - Data derivation: L1 provides "safe transactions/blocks" back to L2; RPC Nodes derive and sync based on L1 data.
- Realtime propagation: Sequencers and RPC Nodes exchange p2p updates so mempools and blocks remain aligned.
- Challengers & security: Challengers validate block assertions on L2 and submit fault proofs to L1 when needed; L1 security is backed by GT staking and validators.
Transaction and Settlement Flow
This sequence diagram details the entire lifecycle of an L2 transaction, from submission to final confirmation. It reveals the interaction sequence between the user, Sequencer, Batcher, Proposer, and GateChain (L1), helping to clarify how a transaction's status evolves from unsafe to finalized.
Component Interaction Diagram
This diagram focuses on the core interactions between different roles in the Gate Layer ecosystem (Users, Nodes, Sequencers, Challengers) and the L1 and L2 layers. It simplifies internal complexities to highlight data flow and the division of responsibilities, such as how users submit transactions, how the Sequencer posts data to L1, and how nodes sync information from L1. 