SatoshiVM
  • Satoshivm
    • Abstract
    • Layer2 Overview
      • Architecture
        • Alpha Mainnet
        • Mainnet
      • Commitment and Verification on Bitcoin
      • Asset Bridge
    • BitVM and SatoshiVM Circuit
    • Preimage Commitment
    • SatoshiVM Scripts and Taproot
    • Verification
    • Framework Visualization
    • Third Party Verification
  • Developer Guide
    • BTC Connect
      • Guide Overview
      • Integrating BTC Connect
      • Quick Summary
    • Contract Address
      • Alpha Mainnet
      • Testnet
  • User Guide
    • Alpha Mainnet
      • Getting Started
      • Network Information
      • Wallet Setup
      • BTC Bridge (Alpha Mainnet)
      • SAVM Bridge (Alpha Mainnet)
      • Ecosystem DApps
        • Savmswap
    • Testnet
      • Getting Started
      • Network Information
      • Wallet Setup
      • Faucet
        • Bridge from Bitcoin
        • Acquire on SatoshiVM
      • BTC Bridge (Testnet)
      • SAVM Bridge (Testnet)
      • BRC20 Bridge (Testnet)
      • Runes Bridge (Testnet)
      • Ecosystem DApps
        • Savmswap
        • SARC-20
  • $SAVM
    • Token Information
    • Token Distribution
    • Token Utility
    • Contract Address
      • Mainnet
      • Testnet
  • roadmap
    • Roadmap
  • Resources
    • Homepage
    • Explorer(Alpha Mainnet)
    • Explorer (Testnet)
    • YellowPaper
    • GitHub
  • COMMUNITY
    • Twitter
    • Discord
    • Telegram
Powered by GitBook
On this page
  1. Satoshivm

Third Party Verification

PreviousFramework VisualizationNextBTC Connect

Last updated 1 year ago

In the previous text, we have detailed the composition of bit commitments Taproot and verification Taproot, and what their being spent signifies, thereby allowing third-party verifiers to determine directly by observing BTC transactions whether the Prover has acted maliciously.

The specific verification process is as follows:

First, observe the spending of the bit commitments Taproot. If the bit commitments Taproot is spent by the Prover, one can proceed to observe the spending of the verification Taproot. If the bit commitments Taproot is spent by the Verifier, it proves that the execution process disclosed by the Prover is inconsistent with the commitment, and it can be directly assumed that the Prover has acted maliciously.

Second, observe the spending of the verification Taproot. If the verification Taproot is spent by the Verifier, it indicates that the execution process provided by the Prover contains errors, and the Prover can be directly considered to have acted maliciously. If the verification Taproot is spent by the Prover, it indicates that there are no errors within the execution process.