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. Core Functionalities

Block Generation

PreviousCore FunctionalitiesNextProof Generation

Last updated 1 month ago

Block generation is a critical process in our system architecture, involving the creation and publication of blocks on both Bitcoin (L1) and VIA (L2) networks. The process consists of the following steps:

  • Transaction Aggregation: The Sequencer collects transactions from the L2 network and aggregates them into multiple new L2 blocks. During this process, the Sequencer runs the transactions in the .

  • Batch Construction: After forming multiple L2 blocks, the Sequencer constructs a corresponding L1 batch using these blocks. This batch includes a summary of the L2 transactions state changes and other necessary metadata to facilitate verification and validation processes.

  • Data Availability: The L1 batch pubdata is published to the data availability layer. By doing this, we ensure that the transaction data remains accessible for specific period of time and verifiable by any entity within the network. This layer plays a crucial role in maintaining the transparency and integrity of the system.

  • Bitcoin Inscription: An optimized block header, summarizing the L1 batch, is inscribed on the Bitcoin blockchain. This step provides a secure and decentralized reference point. The inscription serves as both a commitment to the new L1 batch and a trigger for subsequent processes such as proof generation.

EraVM