zkLLVM Tutorial and Template Project

This repository serves as both a tutorial and a template project for creating an application based on the zkLLVM toolchain. Use it to learn about developing zk-enabled apps with zkLLVM step-by-step.

Prerequisites

For this tutorial, ensure you have an amd64 machine equipped with Docker or Podman (Linux) or Docker Desktop (macOS). For Windows users, Docker in WSL is recommended. While Docker Desktop may work on Windows, it is not officially supported in this tutorial.

Table of Contents

Introduction
Getting started
- 1. Repository setup
- 2. Using the image ghcr.io/nilfoundation/toolchain
Part 1. Circuit development workflow
Part 2. Application developer workflow

Introduction

This tutorial is structured into sequential steps, each executed as a command within the scripts/run.sh script. For first-time users, we strongly recommend utilizing this script.

After completing the tutorial, you can revisit the steps by manually executing commands in the console. Detailed explanations of commands, parameters, file formats, and more can be found under the 🧰 [manual mode] sections in the collapsed blocks.

Getting started

1. Repository setup

Begin by cloning the repository and its submodules:

git clone --recurse-submodules git@github.com:NilFoundation/zkllvm-template.git
cd zkllvm-template

If you initially cloned without --recurse-submodules, update submodules explicitly:

git submodule update --init --recursive

2. Using the image `ghcr.io/nilfoundation/toolchain`

Throughout this tutorial, we'll utilize a Docker image containing the =nil; toolchain:

docker pull ghcr.io/nilfoundation/toolchain:latest

We recommend this specific image as it integrates compatible toolchain components, streamlining the setup process. This image is tagged according to zkLLVM compiler versions, with latest tag always having the latest zkLLVM version. Typically, using the latest image is an optimal choice. For a list of available tags, visit ghcr.io/nilfounation/toolchain.

Part 1. Circuit development workflow

In the first part of this tutorial, we'll walk through the development workflow of a circuit developer. Most operations will be done on a local machine, without using the Proof Market. We will build a circuit, pack it into a circuit statement, and then use it to build a proof for a particular input. Last thing, we'll post the statement on the Proof Market, so that zk application developers will be able to request proofs with this statement.

Code in ./src implements the logic of a storage proof on Ethereum by validating Merkle Tree path of the commited data. It reuses algorithms and data structures from the the Crypto3 C++ high efficiency cryptography library.

Step 1: Compile a circuit

In ./src/main.cpp, we have a function starting with [[circuit]]. This code definition is what we call the circuit itself. We will use zkLLVM compiler to make a byte-code representation of this circuit.

Run the script from the root of your project.

scripts/run.sh --docker compile

The compile command does the following:

Starts a Docker container based on nilfoundation/zkllvm-template.
Makes a clean ./build directory and initializes cmake.
Compiles the code into a circuit.

🧰 [manual mode]

Start a Docker container with the zkLLVM toolchain:

docker run --detach --rm \
    --platform=linux/amd64 \
    --volume $(pwd):/opt/zkllvm-template \
    --user $(id -u ${USER}):$(id -g ${USER}) \
    ghcr.io/nilfoundation/zkllvm-template:0.0.58

Note that it's a single command, wrapped on several lines.

The line --volume $(pwd):/opt/zkllvm-template mounts the project directory from
your host machine into the container, so that the source code is available in it. All the changes will persist on your machine, so you can stop this container at any time, start a new one, and continue.

The line --user $(id -u ${USER}):$(id -g ${USER}) runs container with a user having the same user and group ID as your own user on the host machine. With this option, newly created files in the ./build directory will belong to your user, and not to the root.

Let's check that we have the zkLLVM compiler available in the container. Note that it replaces the original clang, being a fully compatible drop-in replacement:

$ clang --version
clang version 16.0.0 (https://github.com/NilFoundation/zkllvm-circifier.git bf352a2e14522504a0c832f2b66f73268c95e621)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

In the container, create a ./build directory and compile the code:

cd /opt/zkllvm-template
rm -rf build && mkdir build && cd build
cmake -DCIRCUIT_ASSEMBLY_OUTPUT=TRUE ..
make template

The extra parameter DCIRCUIT_ASSEMBLY_OUTPUT=TRUE is required to produce circuits in .ll format, which is supported by proving tools. zkLLVM can also produce circuits in another LLVM's IR format, .bc, but we won't need it in this tutorial.

As a result of this step, we get a byte-code file ./build/src/template.ll. It's a binary file in the LLVM's intermediate representation format.

Step 2: Build a circuit file and an assignment table

Next step is to make a compiled circuit and assignment table.

scripts/run.sh --docker run_assigner

On this step, we run the assigner, giving it the circuit in LLVM IR format (template.lls) and the input data (./src/main-input.json). The assigner produces the following files:

Circuit file ./build/template.crct is the circuit in a binary format that is usable by the proof-generator.
Assignment table ./build/template.tbl is a representation of input data, prepared for proof computation with this particular circuit.

Step 3: Produce and verify a proof locally

Now we have everything ready to produce our first proof. As a circuit developer, we want to first build it locally, to check that our circuit is working. We'll use the proof-generator CLI, which is a part of the =nil; toolchain.

scripts/run.sh --docker prove

🧰 [manual mode]

Run the proof-generator binary to generate a proof:

proof-generator \
    --circuit_input=/opt/zkllvm-template/build/template.json \
    --public_input=/opt/zkllvm-template/src/main-input.json \
    --proof_out=/opt/zkllvm-template/build/template.proof

# --circuit_input: path to the circuit statement
# --public_input: path to the file that contains particular input, that we want to make a proof for
# --proof_out: path and name of the proof file

Note the following lines in the build log:

Preprocessing public data...
Preprocessing private data...
Generating proof...
Proof generated
Proof is verified
...

In the first lines, proof-generator creates a proof, and in the last one it verifies the proof. The resulting proof is in the file ./build/template.proof.

Congratulations! You've produced a non-interactive zero-knowledge proof, or, formally speaking, a zero-knowledge succinct non-interactive argument of knowledge (zk-SNARK).

Now it's time to work with the =nil; Proof Market.

Step 4: Make an account on the Proof Market

To publish statements and order proofs from the Proof Market, you need an account. We'll use the command line tools to create a new one.

First, run a Docker container with the Proof Market toolchain:

cd /opt/zkllvm-template
scripts/run.sh run_proof_market_toolchain

Great, now you're in the container's console. Time to make an account:

cd /proof-market-toolchain
python3 scripts/signup.py user \
    -u <username> \
    -p <password> \
    -e <email>

It should return something like this:

{ "user": "zkdev", "active": true, "extra": {}, "error": false, "code": 201 }

This command will save your username and password in two files in the container:

/proof-market-toolchain/scripts/.user
/proof-market-toolchain/scripts/.secret

These files in the container are mounted to .config/.user and .config/.secret on your machine. This way, when you stop the container, the files will persist until you run it again.

Step 5: Build a circuit statement

The Proof Market works with circuits in the form of circuit statements. A statement is basically a JSON containing the circuit and various metadata that identifies it.

The build_statement command will build a circuit statement from the circuit that we compiled earlier:

scripts/run.sh --docker build_statement

The build_statement command does the following:

Runs a new container based on nilfoundation/proof-market-toolchain.
In the container, runs prepare_statement.py to produce a circuit statement.

🧰 [manual mode]

To build a statement, we will use the prepare_statement.py script, which is a part of the Proof Market toolchain.

First, start a new container with the Proof Market toolchain. Remember to exit the zkllvm container with exit command or start a new console session:

docker run -it --rm \
    --platform=linux/amd64 \
    --volume $(pwd):/opt/zkllvm-template \
    --volume $(pwd)/.config:/.config/ \
    --volume $(pwd)/.config:/root/.config/ \
    --volume $(pwd)/.config/.user:/proof-market-toolchain/scripts/.user \
    --volume $(pwd)/.config/.secret:/proof-market-toolchain/scripts/.secret \
    --volume $(pwd)/../proof-market-toolchain:/proof-market-toolchain/ \
    --user $(id -u ${USER}):$(id -g ${USER}) \
    ghcr.io/nilfoundation/proof-market-toolchain:0.0.33

The .config directory is where you will put the credentials to the Proof Market later on. Two extra volume mounts make this directory available in places where parts of the Proof Market toolchain might look for it.

Now pack the circuit into a statement:

cd /opt/zkllvm-template/
python3 \
    /proof-market-toolchain/scripts/prepare_statement.py \
    --circuit /opt/zkllvm-template/build/src/template.ll \
    --name template \
    --type placeholder-zkllvm \
    --private \
    --output /opt/zkllvm-template/build/template.json

# -c, --circuit: path to the circuit file
# -n, --name: statement name
# -o, --output: path to write the statement file
# --private: make the statement private, as it's not intended for production usage
# -t, --type: type of proofs that will be generated with this statement
# (Placeholder is the name of our proof system, see
# https://crypto3.nil.foundation/papers/placeholder.pdf)

As a result, we have the circuit statement file ./build/template.json. Later we will use it to generate a proof locally. We will also push this circuit statement to the Proof Market.

Step 6: Publish the circuit statement

Remember the statement that we've packed in step 2? Let's publish it on the Proof Market.

python3 scripts/statement_tools.py push \
    --file /opt/zkllvm-template/build/template.json

This command will return the following output with your statement's ID (key):

Statement from /opt/zkllvm-template/build/template.json was pushed with key 12345678.

Step 7: Check the information about your statement

Let's see how the statement is published:

python3 scripts/statement_tools.py get \
    --key 12345678

You should see all the details of your statement in response.

Congratulations! You've built a zkLLVM circuit and published it on the Proof Market. Now it's time to have a look at how developers of zero-knowledge applications use the Proof Market.

Part 2. Application developer workflow

In this part, we will act as a developer of a zk application. Our task is to order a proof on the Proof Market:

Find a circuit statement. We will be using one that has active proof producers, who will respond to our request.
Post a request for a proof with given statement and particular input.
Check that a request was matched and the proof is ready.
Download the proof.

All commands in this section run in the container nilfoundation/proof-market-toolchain:

cd /opt/zkllvm-template
scripts/run.sh run_proof_market_toolchain

Step 1: See the statements available on the Proof Market

First, let's see what statements are available on the Proof Market.

python3 scripts/statement_tools.py get

If you're on a live workshop by =nil;, use the statement with id 96079532. It's built from the circuit code in this template, and accepts input from ./src/main-input.json.

Step 2: Post a proof request

python3 scripts/request_tools.py push \
    --key 96079532 \
    --cost 10 \
    --file /opt/zkllvm-template/src/main-input.json

The output will look like the following, but with different key values.

Limit request:	 {
    "_key": "99887766",
    "statement_key": "96079532",
    "cost": 10,
    "sender": "zkdev",
    "status": "created"
}

Step 3: Check if the proof is ready

You can check the request status at any time:

python3 scripts/request_tools.py get --key 99887766

You should see almost the same output as before. Note the status field: it reflects whether the Proof Market has assigned your request to a particular producer, and whether they have provided the proof.

Limit request:	 {
    "_key": "99887766",
    "statement_key": "96079532",
    "cost": 10,
    "sender": "zkdev",
    "status": "created"
}

Step 4: Download the proof

When the proof is ready, download it:

python3 scripts/proof_tools.py get \
    --request_key 99887766 \
    --file /tmp/example.proof

ls -l /tmp/example.proof

Now the proof can be verified, both off-chain and on-chain. These steps will be added soon.

tldr;

как скомпилить серкет

запустить последовательно

scripts/run.sh --docker compile

scripts/run.sh --docker run_assigner

scripts/run.sh --docker prove

scripts/run.sh --docker build_circuit_params

как проверить пруф ончейн

в build/template будет создана кучка файлов, которые надо положить в https://github.com/NilFoundation/evm-placeholder-verification/tree/master/contracts/zkllvm в папку template

и переименовать файл public-input.json в input.json

имя папки важно

далее по ридми evm-placeholder-verification сделать compile, node, deploy

тест пруфа который получили: npx hardhat verify-circuit-proof --test template

как получить данные для инпутов хэшей в виде двух fields

в ./src/main-input.json инпуты хэшей в виде полей

скрипт для преобразования хэшей из хексов в поля

см ./scripts/gen.py

Name		Name	Last commit message	Last commit date
Latest commit History 93 Commits
.config		.config
.github/workflows		.github/workflows
cmake		cmake
contracts		contracts
libs		libs
scripts		scripts
src		src
storage-proof-app		storage-proof-app
tasks		tasks
.gitignore		.gitignore
.gitmodules		.gitmodules
CMakeLists.txt		CMakeLists.txt
Dockerfile		Dockerfile
Dockerfile.base		Dockerfile.base
README.md		README.md
hardhat.config.ts		hardhat.config.ts
package-lock.json		package-lock.json
package.json		package.json
slither.config.json		slither.config.json
test-task.md		test-task.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

zkLLVM Tutorial and Template Project

Prerequisites

Introduction

Getting started

1. Repository setup

2. Using the image `ghcr.io/nilfoundation/toolchain`

Part 1. Circuit development workflow

Step 1: Compile a circuit

Step 2: Build a circuit file and an assignment table

Step 3: Produce and verify a proof locally

Step 4: Make an account on the Proof Market

Step 5: Build a circuit statement

Step 6: Publish the circuit statement

Step 7: Check the information about your statement

Part 2. Application developer workflow

Step 1: See the statements available on the Proof Market

Step 2: Post a proof request

Step 3: Check if the proof is ready

Step 4: Download the proof

tldr;

как скомпилить серкет

как проверить пруф ончейн

как получить данные для инпутов хэшей в виде двух fields

About

Uh oh!

Releases

Packages

Uh oh!

Contributors

Uh oh!

Languages

Folders and files

Latest commit

History

Repository files navigation

zkLLVM Tutorial and Template Project

Prerequisites

Introduction

Getting started

1. Repository setup

2. Using the image ghcr.io/nilfoundation/toolchain

Part 1. Circuit development workflow

Step 1: Compile a circuit

Step 2: Build a circuit file and an assignment table

Step 3: Produce and verify a proof locally

Step 4: Make an account on the Proof Market

Step 5: Build a circuit statement

Step 6: Publish the circuit statement

Step 7: Check the information about your statement

Part 2. Application developer workflow

Step 1: See the statements available on the Proof Market

Step 2: Post a proof request

Step 3: Check if the proof is ready

Step 4: Download the proof

tldr;

как скомпилить серкет

как проверить пруф ончейн

как получить данные для инпутов хэшей в виде двух fields

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

2. Using the image `ghcr.io/nilfoundation/toolchain`

Packages