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

Proof Verification

Proof verification ensures the integrity and validity of the proofs inscribed on the Bitcoin blockchain based on the corresponding L1 batch. It involves the following steps:

  • Notifier and Data Retrieval: When a new proof is committed on Bitcoin by the Proposer’s inscription, the Via Inscription Indexer within the Verifier Node notifies the necessary components once the proof commitment transaction is confirmed. Each Verifier then retrieves the required data, including the L1 batch header and the proof itself.

  • Proof Verification: The Verifier uses the Zero-Knowledge Proof verification key to validate the SNARK proof. This step involves checking the correctness of the proof against the L1 batch header to ensure that the transactions and state changes within the batch are valid.

  • Attestation: The Verifier inscribes the attestation data to the Bitcoin network. Each attestation indicates whether the Verifier considers the proof valid or invalid.

PreviousProof GenerationNextBlock Finality

Last updated 3 months ago