Submitting proofs

Make sure you have Aligned installed as specified here.

If you run the examples below, make sure you are in Aligned's repository root.

You can check your submitted proofs on Mainnet Explorer and Holesky Explorer.

Supported Verifiers

The following is the list of the verifiers currently supported by Aligned:

✅ gnark - Groth16 (with BN254) (v0.12.0)
✅ gnark - Plonk (with BN254 and BLS12-381) (v0.12.0)
✅ SP1 (v5.0.0)
✅ Risc0 (v2.0.0)

Learn more about future verifiers here.

1. Import/Create Keystore file

If you already have a keystore file, you can ignore this section and start sending proofs. We give two examples of how to generate one. The first one using Foundry, and the second one using EigenLayer CLI

Alternative 1: With foundry

You need to have installed Foundry.

When creating a new wallet keystore and private key please use strong passwords for your own protection.

If you are creating a new account, create a private key with:

cast wallet new-mnemonic --words 12

It will show you a new mnemonic phrase and a public-private key pair, similar to the following example:

Phrase:
test test test test test test test test test test test test

Accounts:
- Account 0:
Address:     0xabcd...1234
Private key: 0x1234...abcd

Import the wallet using the private key previously generated, or whichever you want to use, and write a password to use it.
```
mkdir -p ~/.aligned_keystore/
cast wallet import ~/.aligned_keystore/keystore0 --interactive
```
You have to paste your private key and set a password for the keystore file.

This will create the ECDSA keystore file in ~/.aligned_keystore/keystore0

Alternative 2: With EigenLayer CLI

If you have the EigenLayer CLI installed, the keystore can be generated following these instructions. The key will be stored into ~/.eigenlayer/operator_keys.

2. Send funds to Aligned

To send proofs to Aligned using the Batcher, the user must first deposit some funds in Aligned to pay for the verification of his proofs.

To use it, you can use the aligned CLI, as shown with the following example:

aligned deposit-to-batcher \
--rpc_url https://ethereum-holesky-rpc.publicnode.com \
--network holesky \
--keystore_path <keystore_path> \
--amount 0.1ether

This command allows the usage of the following flags:

--rpc_url to specify the rpc url to be used.
--network to specify the network to be used. Can be devnet, holesky or mainnet.
--keystore_path the path to the keystore.
--amount the number of ethers to transfer to the Batcher.
Note: --amount flag parameter must be with the shown format, XX.XXether.

After depositing funds, you can verify the Service has correctly received them by executing the following command:

aligned get-user-balance \
--rpc_url https://ethereum-holesky-rpc.publicnode.com \
--network holesky \
--user_addr <user_addr>

These commands allow the usage of the following flags:

--rpc_url to specify the rpc url to be used.
--network to specify the network to be used. Can be devnet, holesky or mainnet.
--user_addr the address of the user that funded the Batcher.

3. Submit your proof to the batcher

This guide will focus on how to submit proofs using the Aligned CLI. To integrate the proof submission process into your application, check the First Aligned Application tutorial where we explain how to generate and submit a proof using the Aligned SDK.

Proof submission is done via the submit command of the Aligned CLI. The arguments for the submit command are:

proving_system: The proving system corresponding to the proof you want to submit.
proof: The path of the proof associated to the computation to be verified.
vm_program: When the proving system involves the execution of a program in a zkVM, this argument is associated with the compiled program or some other identifier of the program.
pub_input: The path to the file with the public input associated with the proof.
One of the following, to specify which Network to interact with:
- --network <working_network_name>: Network name to interact with.
  - Default: devnet
  - Possible values: devnet, holesky, mainnet
- For a custom Network, you must specify the following parameters:
  - --aligned_service_manager <aligned_service_manager_contract_address>
  - --batcher_payment_service <batcher_payment_service_contract_address>
  - --batcher_url <batcher_websocket_url>
rpc_url: The RPC Ethereum node URL.
proof_generator_addr: An optional parameter that can be used in some applications to avoid front-running.
batch_inclusion_data_directory_path: An optional parameter indicating the directory where to store the batcher response data. If not provided, the folder with the responses will be created in the current directory.

SP1 proof

The current SP1 version used in Aligned is v5.0.0.

The SP1 proof needs the proof file and the vm program file.

rm -rf ./aligned_verification_data/ &&
aligned submit \
--proving_system SP1 \
--proof <proof_file> \
--vm_program <vm_program_file> \
--proof_generator_addr [proof_generator_addr] \
--batch_inclusion_data_directory_path [batch_inclusion_data_directory_path] \
--keystore_path <path_to_ecdsa_keystore> \
--network holesky \
--rpc_url https://ethereum-holesky-rpc.publicnode.com

Example

rm -rf ./aligned_verification_data/ &&
aligned submit \
--proving_system SP1 \
--proof ./scripts/test_files/sp1/sp1_fibonacci_5_0_0.proof \
--vm_program ./scripts/test_files/sp1/sp1_fibonacci_5_0_0.elf \
--keystore_path ~/.aligned_keystore/keystore0 \
--network holesky \
--rpc_url https://ethereum-holesky-rpc.publicnode.com

Risc0 proof

The current Risc0 version used in Aligned is v2.0.0.

The Risc0 proof needs the proof file and the vm program file (vm program file is the image id).

rm -rf ./aligned_verification_data/ &&
aligned submit \
--proving_system Risc0 \
--proof <proof_file> \
--vm_program <vm_program_file> \
--pub_input <pub_input_file> \
--proof_generator_addr [proof_generator_addr] \
--batch_inclusion_data_directory_path [batch_inclusion_data_directory_path] \
--keystore_path <path_to_ecdsa_keystore> \
--network holesky \
--rpc_url https://ethereum-holesky-rpc.publicnode.com

NOTE: As said above, Aligned currently supports Risc0 proofs from risc0-zkvm version v2.0.0. For generating proofs using cargo risc-zero please ensure you are using v2.0.0 or your proof will not be verified.

If you can't install cargo-risczero v2.0.0, you can manually modify your cargo.toml on the host project to point to v2.0.0:

risc0-zkvm = { git = "https://github.com/risc0/risc0", tag = "v2.0.0", default-features = false, features = [
    "prove",
] }

Note: In Risc0 verification --pub_input contains the bytes of the receipt.journal.bytes which contains both the public input (env::read()) and public output (env::commit()) values of a program executed in the Risc0 VM. If your Risc0 program contains public outputs, but no public inputs you still need to submit the serialized receipt.journal.bytes with your proof using the Aligned CLI for your proof to be verified.

Example

rm -rf ~/.aligned/aligned_verification_data/ &&
aligned submit \
--proving_system Risc0 \
--proof ./scripts/test_files/risc_zero/fibonacci_proof_generator/risc_zero_fibonacci_2_0.proof \
--vm_program ./scripts/test_files/risc_zero/fibonacci_proof_generator/fibonacci_id_2_0.bin \
--public_input ./scripts/test_files/risc_zero/fibonacci_proof_generator/risc_zero_fibonacci_2_0.pub \
--aligned_verification_data_path ~/.aligned/aligned_verification_data \
--keystore_path ~/.aligned_keystore/keystore0 \
--network holesky \
--rpc_url https://ethereum-holesky-rpc.publicnode.com

GnarkPlonkBn254, GnarkPlonkBls12_381 and Groth16Bn254

The GnarkPlonkBn254, GnarkPlonkBls12_381 and Groth16Bn254 proofs need the proof file, the public input file and the verification key file.

rm -rf ./aligned_verification_data/ &&
aligned submit \
--proving_system <GnarkPlonkBn254|GnarkPlonkBls12_381|Groth16Bn254> \
--proof <proof_file> \
--public_input <public_input_file> \
--vk <verification_key_file> \
--proof_generator_addr [proof_generator_addr] \
--batch_inclusion_data_directory_path [batch_inclusion_data_directory_path] \
--keystore_path <path_to_ecdsa_keystore> \
--network holesky \
--rpc_url https://ethereum-holesky-rpc.publicnode.com

Examples:

rm -rf ./aligned_verification_data/ &&
aligned submit \
--proving_system GnarkPlonkBn254 \
--proof ./scripts/test_files/gnark_plonk_bn254_script/plonk_0_12_0.proof \
--public_input ./scripts/test_files/gnark_plonk_bn254_script/plonk_pub_input_0_12_0.pub \
--vk ./scripts/test_files/gnark_plonk_bn254_script/plonk_0_12_0.vk \
--keystore_path ~/.aligned_keystore/keystore0 \
--network holesky \
--rpc_url https://ethereum-holesky-rpc.publicnode.com

rm -rf ./aligned_verification_data/ &&
aligned submit \
--proving_system GnarkPlonkBls12_381 \
--proof ./scripts/test_files/gnark_plonk_bls12_381_script/plonk_0_12_0.proof \
--public_input ./scripts/test_files/gnark_plonk_bls12_381_script/plonk_pub_input_0_12_0.pub \
--vk ./scripts/test_files/gnark_plonk_bls12_381_script/plonk_0_12_0.vk \
--keystore_path ~/.aligned_keystore/keystore0 \
--network holesky \
--rpc_url https://ethereum-holesky-rpc.publicnode.com

rm -rf ./aligned_verification_data/ &&
aligned submit \
--proving_system Groth16Bn254 \
--proof ./scripts/test_files/gnark_groth16_bn254_script/groth16_0_12_0.proof \
--public_input ./scripts/test_files/gnark_groth16_bn254_script/groth16_0_12_0.pub \
--vk ./scripts/test_files/gnark_groth16_bn254_script/groth16_0_12_0.vk \
--keystore_path ~/.aligned_keystore/keystore0 \
--network holesky \
--rpc_url https://ethereum-holesky-rpc.publicnode.com

PreviousDeep Dive NextBuild your first Aligned Application

Last updated 18 days ago