From 1ec84f08b582adb1c4a56cc66db2370725d12bb8 Mon Sep 17 00:00:00 2001 From: pecornilleau Date: Wed, 26 Oct 2022 09:47:02 +0200 Subject: [PATCH] Wasm: set value for wasm_max_tick --- src/lib_scoru_wasm/constants.ml | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/src/lib_scoru_wasm/constants.ml b/src/lib_scoru_wasm/constants.ml index f1a3ecccb7ae..d56da146668d 100644 --- a/src/lib_scoru_wasm/constants.ml +++ b/src/lib_scoru_wasm/constants.ml @@ -31,11 +31,17 @@ let wasm_main_module_name = "main" kernel to expose a function named [kernel_next]. *) let wasm_entrypoint = "kernel_next" -(* TODO: https://gitlab.com/tezos/tezos/-/issues/3590 - An appropriate number should be used, - currently 100 times the nb of ticks it takes tx_kernel to init, deposit, then withdraw - (so 100x 2 billion ticks) *) -let wasm_max_tick = Z.of_int 200_000_000_000 +(* Number of ticks between snapshotable states, + should be chosen low enough to maintain refutability. + + Depends on + - speed (tick/s) of node in slow mode (from benchmark, 6000000 tick/s) + - the number of ticks in a commitment (Int64.max_int, + as per Number_of_ticks.max_value) + + see #3590 for more pointers +*) +let wasm_max_tick = Z.of_int 11_000_000_000 (* TODO: https://gitlab.com/tezos/tezos/-/issues/3157 Find an appropriate number of reboots per inputs. -- GitLab