Running the Demo

Note: The demo currently simulates the rollup at the transaction engine level — it does not connect to a live Kaspa network. The host builds a mock chain with mock blocks and transactions, generates real ZK proofs over them, and verifies the proofs through the actual on-chain script logic (covenant + permission scripts executed via kaspa-txscript). This validates the full proof pipeline and script verification end-to-end, without requiring a running node.

Prerequisites

• Rust stable toolchain
• RISC Zero toolchain (rzup)

For CUDA-accelerated proving (optional):

• NVIDIA GPU with CUDA support
• CUDA toolkit installed

Building and running

All commands must be run from the host/ directory:

cd examples/zk-covenant-rollup/host

CPU proving (default)

cargo run --release

CUDA-accelerated proving

cargo run --release --features cuda

Adding non-activity blocks

The --non-activity-blocks=N flag adds N blocks filled with 3000 non-action (V0) transactions each. This stress-tests the sequence commitment logic — the guest must iterate through all transactions to verify the seq commitment even though none of them are L2 actions.

cargo run --release -- --non-activity-blocks=5

Combined with CUDA:

cargo run --release --features cuda -- --non-activity-blocks=5

What the demo does

1. Builds an initial empty SMT (sparse Merkle tree) state
2. Constructs a mock chain with L2 action transactions (deposits, transfers, exits)
3. Generates a STARK (succinct) proof via RISC Zero and verifies it
4. Simulates on-chain verification of the STARK proof through the covenant script
5. Generates a Groth16 proof and verifies it
6. Simulates on-chain verification of the Groth16 proof through the covenant script
7. If exits occurred, verifies the permission script flow as well