Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 20 additions & 3 deletions docs/getting-started/running-the-prover.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,18 +75,35 @@ docker run --rm -v "$PWD:/work" somnergy/z6m_prover \
execute --block-number 23100000 --data-dir /work/data
```

Proving a block on GPU for a single block can be initiated as follows:
Proving a single block on GPU is done with service mode, bounded to one block:

```bash
docker run --rm --gpus all --network host \
-v /var/run/docker.sock:/var/run/docker.sock \
-v "$PWD:/work" \
-e SP1_PROVER=cuda \
somnergy/z6m_prover:latest \
prove --block-number 23100000 --data-dir /work/data
--service --rpc-url "$RPC_URL" --data-dir /work/data \
--start-block 23100000 --end-block 23100000 \
--prove-every 1 --proof-type compressed
```

The proof is written to `<data-dir>/<block>/proof<block>.bin` — here
`/work/data/23100000/proof23100000.bin`. Service mode fetches the block and its witness itself, so no separate
`fetch` run is needed.

:::warning
Use service mode, not the one-shot `prove` subcommand, whenever you need the proof **on disk**. `prove` keeps the
proof in memory and never writes it, ignores `--proof-path`, and exits 0 even when proving fails — see

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bounded service run also exits 0 when fetching or proving fails, so this is no contrast with prove.

[`prove` in the CLI reference](cli-reference.md#prove). Two flags above are load-bearing: `SP1_PROVER=cuda` (any

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Contradicts the SP1_PROVER modes table below: mock and network also fall back to the CPU prover.

other value, or unset, silently selects the CPU prover) and `--prove-every 1` (it is a modulo on the block number
and defaults to *never*, so omitting it proves nothing).
:::

The docker image builds with `CUDA_ARCHS="89,90,100"` so it already bakes in support for the latest NVIDIA GPU architectures for SP1-GPU.
To prove the blocks in a continuous fashion, you can use the `--service` mode as follows:

To keep proving continuously instead, drop the block bounds and widen the interval — with `--prove-every 100`, only
blocks whose number is divisible by 100 are proved:

```bash
z6m_prover --service --rpc-url "$RPC_URL" --data-dir /mnt/data \
Expand Down
5 changes: 5 additions & 0 deletions docs/testing/ethereum-execution-tests-eests.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,9 +36,14 @@ Before running the tests, make sure the following tools are installed:
* `git,git-lfs`
* `python3,python3-pip,pipx`
* `ctest` (usually shipped with CMake, but ensure it’s available on your PATH)
* `rust/cargo` — see [rustup.rs](https://rustup.rs)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On master eest-blockchain-tests builds z6m_eest_convert with CMake; there is no eest-rlp-build target and no cargo step.


> `git-lfs` is required because some test fixtures have very large files.

> Rust is required even though the tests themselves are C++: `eest-blockchain-tests` depends on `eest-rlp-build`,
> which builds the `z6m_eest_convert` fixture converter with `cargo build --release`. That build also resolves the
> `erigontech/sp1` git dependency, so the first run takes a while.

#### Clone the repository

Get the latest source for Zilkworm
Expand Down
4 changes: 2 additions & 2 deletions docs/testing/riscv-testing-eests-on-rv32im-via-qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,8 +53,8 @@ git submodule foreach 'git lfs pull'
#### **Run EEST blockchain tests on RV32IM (via QEMU)**

```bash
cd zilkworm/qemu_runner
make rv32im_eest_blockchain_tests
cd qemu_runner
make eest-rv32
```

That would build the project for rv32im and invoke `ctest` to launch a bunch of `qemu-system-riscv32` instances in the background. Each of these instances is passed with a JSON file to run as a test.\
Expand Down
7 changes: 4 additions & 3 deletions src/pages/index.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -102,9 +102,10 @@ const capabilities: Card[] = [
},
];

const exampleCommand = `// Create block proofs in one command
z6m_prover prove --block-number 23456789 --proof-path proof.json
z6m_prover verify proof.json`;
const exampleCommand = `# Prove an Ethereum mainnet block on GPU
SP1_PROVER=cuda z6m_prover --service --rpc-url $RPC_URL --data-dir ./data \\
--start-block 23456789 --end-block 23456789 --prove-every 1
# → ./data/23456789/proof23456789.bin`;

export default function Home(): React.ReactElement {
return (
Expand Down
32 changes: 27 additions & 5 deletions static/llms-full.txt
Original file line number Diff line number Diff line change
Expand Up @@ -710,18 +710,35 @@ docker run --rm -v "$PWD:/work" somnergy/z6m_prover \
execute --block-number 23100000 --data-dir /work/data
```

Proving a block on GPU for a single block can be initiated as follows:
Proving a single block on GPU is done with service mode, bounded to one block:

```bash
docker run --rm --gpus all --network host \
-v /var/run/docker.sock:/var/run/docker.sock \
-v "$PWD:/work" \
-e SP1_PROVER=cuda \
somnergy/z6m_prover:latest \
prove --block-number 23100000 --data-dir /work/data
--service --rpc-url "$RPC_URL" --data-dir /work/data \
--start-block 23100000 --end-block 23100000 \
--prove-every 1 --proof-type compressed
```

The proof is written to `<data-dir>/<block>/proof<block>.bin` — here
`/work/data/23100000/proof23100000.bin`. Service mode fetches the block and its witness itself, so no separate
`fetch` run is needed.

:::warning
Use service mode, not the one-shot `prove` subcommand, whenever you need the proof **on disk**. `prove` keeps the
proof in memory and never writes it, ignores `--proof-path`, and exits 0 even when proving fails — see
[`prove` in the CLI reference](cli-reference.md#prove). Two flags above are load-bearing: `SP1_PROVER=cuda` (any
other value, or unset, silently selects the CPU prover) and `--prove-every 1` (it is a modulo on the block number
and defaults to *never*, so omitting it proves nothing).
:::

The docker image builds with `CUDA_ARCHS="89,90,100"` so it already bakes in support for the latest NVIDIA GPU architectures for SP1-GPU.
To prove the blocks in a continuous fashion, you can use the `--service` mode as follows:

To keep proving continuously instead, drop the block bounds and widen the interval — with `--prove-every 100`, only
blocks whose number is divisible by 100 are proved:

```bash
z6m_prover --service --rpc-url "$RPC_URL" --data-dir /mnt/data \
Expand Down Expand Up @@ -853,9 +870,14 @@ Before running the tests, make sure the following tools are installed:
* `git,git-lfs`
* `python3,python3-pip,pipx`
* `ctest` (usually shipped with CMake, but ensure it’s available on your PATH)
* `rust/cargo` — see [rustup.rs](https://rustup.rs)

> `git-lfs` is required because some test fixtures have very large files.

> Rust is required even though the tests themselves are C++: `eest-blockchain-tests` depends on `eest-rlp-build`,
> which builds the `z6m_eest_convert` fixture converter with `cargo build --release`. That build also resolves the
> `erigontech/sp1` git dependency, so the first run takes a while.

#### Clone the repository

Get the latest source for Zilkworm
Expand Down Expand Up @@ -934,8 +956,8 @@ git submodule foreach 'git lfs pull'
#### **Run EEST blockchain tests on RV32IM (via QEMU)**

```bash
cd zilkworm/qemu_runner
make rv32im_eest_blockchain_tests
cd qemu_runner
make eest-rv32
```

That would build the project for rv32im and invoke `ctest` to launch a bunch of `qemu-system-riscv32` instances in the background. Each of these instances is passed with a JSON file to run as a test.\
Expand Down