Risc0 to BitVM

Warning: This software is experimental and should not be used in production.

Building Risc0 Guests

To build Risc0 guests deterministically, run the following command:

REPR_GUEST_BUILD=1 cargo build --release

Proving Bitcoin Headers

To prove Bitcoin headers, first download the Bitcoin headers:

wget https://zerosync.org/chaindata/headers.bin

Usage

./target/release/core None first_10.bin 10

• The first argument is the previous proof file path (None if starting from genesis).
• The second argument is the output proof file path.
• The third argument is the number of headers to prove.

Example: To verify the previous proof and prove the next 90 Bitcoin headers, run the following command:

./target/release/core first_10.bin first_100.bin 90

Risc0 to Succinct Proofs

BitVM requires a Groth16 proof with one public input. We have implemented the necessary functionalities to support this.

Setup

First download the STARK Verify Circom circuit:

git lfs pull

Then download Powers of Tau ceremony files:

wget -O ./groth16_proof/groth16/pot23.ptau https://storage.googleapis.com/zkevm/ptau/powersOfTau28_hez_final_23.ptau

To run the ceremony for groth16 proof:

cd groth16_proof
docker build -f docker/ceremony.Dockerfile . -t snark-ceremony
docker run --rm -v $(pwd)/groth16:/ceremony/groth16_proof/groth16 snark-ceremony

To build the prover:

docker build -f docker/prover.Dockerfile . -t risc0-groth16-prover

Testing

To test the setup, use:

cargo test -r --package core --bin core -- tests --show-output

Our Approach

Goal

Our goal is to be able to (optimistically) prove any computation inside BitVM. Overall system is as follows:

Here, the journals with non-constant sizes of the general-purpose circuits will be digested (etc. hashing using Blake3) with the circuit constants (general_purpose_circuit_method_id, final_circuit_method_id, pre_state, post_state, etc.) in BitVM to ensure the correctness of the claims.

Bitcoin

In the case of Bitcoin, the main computations we want to prove are the bridge operations (PegIn/PegOut). This requires the proving of the Bitcoin block headers. With header-chain-circuit, one can prove the current state of the Bitcoin given the block headers. It does not necessarily prevent the malicious actors to generate proofs for their private forks, but the calculation of the ChainState is the basis for the conflict resolution. For more, see: Proof of work.

Acknowledgments

• Risc0: This repository is built using the technology stack of Risc0, more specifically Risc0 ZKVM and their STARK verifier Circom circuit.
• Blake3 Circom: The Circom circuit of the Blake3 hash function implementation is taken from here.
• Bitcoin Header Chain Proof: Our Bitcoin header chain proof circuit implementation is inspired by the Bitcoin Core implementation and ZeroSync's header chain proof circuit.