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
  • Introduction
  • Architecture Overview
  • Verifier Network Flows
  • Block Finalization
  • Withdrawal Processing
  • Current Limitations
  1. Technical Specs

Verifier Network

Explore the basic concepts and flows related to the Verifier Network.

PreviousInscription StandardNextBridge BTC between Bitcoin and VIA

Last updated 1 month ago

This document provides an overview of the Verifier Network architecture, main flows related to the network and current system limitations to be addressed in future releases.

Introduction

The Verifier Network is a crucial component of the VIA Protocol, responsible for validating Zero-Knowledge (ZK) proofs and ensuring the integrity of off-chain execution.

Architecture Overview

The Verifier Network consists of multiple Verifier Nodes with the main goal of verifying ZK (SNARK) proofs for L1 batches, generated by the Prover. These nodes attest to the validity of the L2 state transitions, before the batches are finalized and withdrawals are processed. One of the Verifier Nodes acts as a Coordinator Node whose main responsibility is to manage the signing sessions, coordinate the Simple Two-Round Schnorr Multi-Signatures () process for transaction signing and broadcast the signed transaction to the Bitcoin network.

Verifier Network Flows

The following sections explain the roles of the Verifier Network partitipants in different flows.

Block Finalization

  • Batch and proof metadata are inscribed on the Bitcoin network by the Sequencer.

  • Verifier detects the new proof inscription.

  • It obtains the proof and batch data from the Celestia network.

  • Batch proof verification is performed.

  • After the verification, each Verifier Node sends the attestation inscription to the Bitcoin network.

  • Once the required number of attestations (majority) is detected, indicating the ZK proof validity, the L1 batch is considered final.

Withdrawal Processing

  • After the L1 batch is final, Coordinator starts the withdrawal signing session.

  • Each Verifier periodically polls the Coordinator API to obtain the new signign session.

  • The Coordinator orchestrates the MuSig2 signing process.

  • After the successful generation of the aggragated signature, Coordinator broadcasts the withdrawal transaction to the Bitcoin network.

Current Limitations

To explore the known limitations of the Verifier Network design, check the page.

MuSig2
System Constraints and Design Trade-offs