From d93717c4fe6df6451eeac6b05279c39d7927bb93 Mon Sep 17 00:00:00 2001 From: Rohit Narurkar Date: Thu, 18 Jul 2024 11:38:17 +0100 Subject: [PATCH] fix: vk filenames --- prover/src/consts.rs | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/prover/src/consts.rs b/prover/src/consts.rs index 1cebefccc4..978594092d 100644 --- a/prover/src/consts.rs +++ b/prover/src/consts.rs @@ -4,19 +4,17 @@ use std::sync::LazyLock; // TODO: is it a good design to use LazyLock? Why not read env var each time? pub fn bundle_vk_filename() -> String { - read_env_var("BUNDLE_VK_FILENAME", "bundle_vk.vkey".to_string()) + read_env_var("BUNDLE_VK_FILENAME", "vk_bundle.vkey".to_string()) } pub fn batch_vk_filename() -> String { - read_env_var("BATCH_VK_FILENAME", "batch_vk.vkey".to_string()) + read_env_var("BATCH_VK_FILENAME", "vk_batch.vkey".to_string()) } pub fn chunk_vk_filename() -> String { - read_env_var("CHUNK_VK_FILENAME", "chunk_vk.vkey".to_string()) + read_env_var("CHUNK_VK_FILENAME", "vk_chunk.vkey".to_string()) } pub static CHUNK_PROTOCOL_FILENAME: LazyLock = LazyLock::new(|| read_env_var("CHUNK_PROTOCOL_FILENAME", "chunk.protocol".to_string())); -pub static BATCH_PROTOCOL_FILENAME: LazyLock = - LazyLock::new(|| read_env_var("BATCH_PROTOCOL_FILENAME", "batch.protocol".to_string())); pub static CHUNK_VK_FILENAME: LazyLock = LazyLock::new(chunk_vk_filename); pub static BATCH_VK_FILENAME: LazyLock = LazyLock::new(batch_vk_filename);