Architecture Overview

System Architecture Diagram

Network Componenfts

1. Main Node

The Main Node serves as the primary processing unit of the L3 blockchain network.

Key Responsibilities:

• Instant transaction validation and confirmation

• User request processing

• Maintenance of current network state

• Regular updates to sequencer nodes

Technical Specifications:

• Single node operation for maximum efficiency

• High-performance processing capabilities

• Real-time state management

• Robust failover mechanisms

2. Sequencer Nodes

Sequencers form a critical layer in the transaction processing pipeline.

Functions:

• Collection of validated transactions

• Transaction compression and batching

• Distribution of batches to Provers

• Submission of proofs to L2 Verifier

Operation Process:

• Receive state updates from Main Node

• Create optimized transaction batches

• Coordinate with Provers for proof generation

• Manage state transition verifications

3. Provers

Provers are responsible for generating cryptographic proofs of transaction validity.

Core Functions:

• Receipt of transaction batches from Sequencers

• Generation of zero-knowledge proofs

• Validation of state transitions

• Proof submission back to Sequencers

Technical Implementation:

• Parallel proof generation

• Optimized computational processes

• Scalable proof creation system

• Efficient verification mechanisms

4. L2 Verifier

The L2 Verifier serves as the security bridge between L3 and L2 networks.

Primary Responsibilities:

• Verification of proofs from Sequencers

• State commitment on L2

• Security assurance

• Cross-chain transaction validation

System Flow

Data Flow Architecture

The data flow diagram demonstrates the complete lifecycle of transactions and data in our system:

1. Transaction Submission (TX → Main Node)

   • Users submit transactions to the Main Node

   • Initial validation and processing

2. Batch Processing (Main Node → Sequencers)

   • Transactions are batched for efficient processing

   • Sequencers prepare data for proof generation

3. Proof Generation (Sequencers ↔ Provers)

   • Provers generate zero-knowledge proofs

   • Proofs are returned to Sequencers

4. State Verification (Sequencers → Verifier)

   • Proofs are submitted for verification

   • State updates are confirmed

5. State Synchronization (Verifier → System)

   • Verified states are synchronized across the system

   • Main Node receives state updates

Transaction Processing Flow

The system processes transactions through the following stages:

1. User submission to Main Node

2. Instant validation and confirmation

3. Batch processing by Sequencers

4. Proof generation by Provers

5. L2 verification and commitment

State Management

1. State Updates:

   • Real-time processing on Main Node

   • Periodic state snapshots

   • Compressed state transitions

   • L2 state commitments

2. Synchronization:

   • Regular state updates to Sequencers

   • Verification of state consistency

   • Resolution of state conflicts

   • Recovery procedures

Security Architecture

Multi-layer Security Model:

1. Transaction Level:

   • Signature verification

   • Balance validation

   • Double-spend prevention

   • Transaction format validation

2. Network Level:

   • Node authentication

   • Secure communication channels

   • DDoS protection

   • Traffic monitoring

3. State Level:

   • Zero-knowledge proofs

   • State verification on L2

   • Regular state commitments

   • Conflict resolution mechanisms

Integration with L2

Connection to StarkNet:

1. State Commitments:

   • Regular state root submissions

   • Proof verification

   • Security anchoring

   • Cross-chain communication

2. Bridge Operations:

   • Asset deposits

   • Withdrawal processing

   • Cross-chain message passing

   • Emergency procedures