VIA Protocol
  • Getting Started
    • Introduction
  • Technical Specs
    • Architecture Overview
    • Core Functionalities
      • Block Generation
      • Proof Generation
      • Proof Verification
      • Block Finality
    • Transaction Flows Overview
      • L2 Transactions
      • Deposits
      • Withdrawals
    • Inscription Standard
    • Verifier Network
  • User Guide
    • Bridge BTC between Bitcoin and VIA
    • Get VIA Testnet BTC
    • Run VIA Verifier Node
  • Developer Docs
    • Quickstart
    • Tooling
    • 🛰️ RPC Documentation
    • Connect to VIA Network
  • Future Research
    • System Constraints and Design Trade-offs
    • Trust-minimized BTC Bridge
  • FAQs & Troubleshooting
    • FAQs
    • Contact & Support
Powered by GitBook
On this page
  1. Technical Specs
  2. Transaction Flows Overview

L2 Transactions

PreviousTransaction Flows OverviewNextDeposits

Last updated 1 month ago

The flow for a VIA L2 transaction (contract call, contract deployment, or user-to-user transfer) begins when a user submits a transaction through RPC calls to the Sequencer’s mempool. The Sequencer’s State Keeper component is then responsible for constructing a new L2 block and an associated L1 batch based on various sealing criteria.

For a detailed explanation of the sealing conditions, refer to . To understand how EraVM operates and how transactions are processed, see the or check . This aspect of the protocol is fully inherited in the VIA Protocol.

ZKsync’s L2 Block Sealing
transaction workflow overview
ZKsync's official documentation