From eefb57f2c035be1a398f630dd8cfed8b4ccbe348 Mon Sep 17 00:00:00 2001 From: Kamen Mladenov Date: Wed, 30 Apr 2025 17:25:15 +0300 Subject: feat(zkvms_guest_io): Output proof size In each zkVM we'll write the size to /tmp/proof_size and then guest_io will read that value and place it inside our metrics output. This is not the most elegant, and in certain zkVMs the file output is a part of the benchmark timing, but it will have to do. --- zkvms/zkm/host/src/main.rs | 3 +++ 1 file changed, 3 insertions(+) (limited to 'zkvms/zkm') diff --git a/zkvms/zkm/host/src/main.rs b/zkvms/zkm/host/src/main.rs index 3b8d068..1640b30 100644 --- a/zkvms/zkm/host/src/main.rs +++ b/zkvms/zkm/host/src/main.rs @@ -9,6 +9,7 @@ use zkm_sdk::{ use zkvms_host_io::{ benchmarkable, read_args, RunType::{Execute, Prove, Verify}, + output_proof_size, }; async fn get_proof( @@ -40,6 +41,8 @@ async fn prove( ) { let prover_result = get_proof(prover_client, prover_input).await; + output_proof_size(&prover_result); + prover_client .process_proof_results(&prover_result, &prover_input, &proof_results_path) .expect("process proof results error"); -- cgit v1.2.3