# Third Party Verification

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:

<figure><img src="/files/hWolUkQoW5kVwivSplqn" alt=""><figcaption></figcaption></figure>

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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.satoshivm.io/satoshivm/third-party-verification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.