Closed Nashtare closed 2 months ago
It's plausible! could you paste instructions on how to repro?
Sure. I've replaced the circuit sizes in prove_stdio.sh
with
export ARITHMETIC_CIRCUIT_SIZE="16..26"
export BYTE_PACKING_CIRCUIT_SIZE="8..23"
export CPU_CIRCUIT_SIZE="12..25"
export KECCAK_CIRCUIT_SIZE="14..23"
export KECCAK_SPONGE_CIRCUIT_SIZE="9..20"
export LOGIC_CIRCUIT_SIZE="12..22"
export MEMORY_CIRCUIT_SIZE="17..28"
and on the branch / commit mentioned, running ./prove_stdio.sh witness.json
Note that you may need to set -n 1
(num workers) or use a powerful machine to handle the RAM consumption.
This one has not been observed / reproduced since proper stabilization of zero-bin
post migration into zk_evm
and correct handling around circuit persistence logic, hence will close for now and reopen if it ever occurs again.
It seems there's some inconsistency in circuit fetching when running
zero-bin
with--load-strategy on-demand
. In particular it seems to always affect theMemory
circuit.The logs seem to highlight the expected configuration is running:
where the
Memory
range is17..28
.Several witnesses failed with following errors:
When inspecting
zero_bin/circuits
it seems the circuits have been properly written to disk:Obtained on
zk_evm@feat/cancun
, commit ddca6be9a40a7d0492312ecaf9d966e2124dbc91.Side note: