From f3f511af266dcd8fb54a1ec8f382ce24cf704d6c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juli=C3=A1n=20Gonz=C3=A1lez=20Calder=C3=B3n?= Date: Tue, 1 Oct 2024 15:28:32 -0300 Subject: [PATCH] Update README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e815fce..91fb871 100644 --- a/README.md +++ b/README.md @@ -96,11 +96,11 @@ RUST_LOG=replay=error cargo run block mainnet 648461 ### Comparing with VM To compare Native execution with the VM, you can use the `state_dump` feature. It will save to disk the execution info and state diff of every contract executed. -- If executing Native, the dumps will be saved at: `state_dumps/native/{tx_hash}.json` -- If paired with `only_cairo_vm` feature, the dumps will be saved at: `state_dumps/vm/{tx_hash}.json` +- If executing Native, the dumps will be saved at: `state_dumps/native/block{block_number}/{tx_hash}.json` +- If paired with `only_cairo_vm` feature, the dumps will be saved at: `state_dumps/vm/block{block_number}/{tx_hash}.json` To compare the outputs, you can use the following scripts. Some of them required `delta` (modern diff). -- `cmp_state_dumps.sh`. Prints which transactions match with the VM and which differ. It moves matching transaction to another directory `good_state_dump`. +- `cmp_state_dumps.sh`. Prints which transactions match with the VM and which differ. ```bash > ./scripts/cmp_state_dumps.sh diff: 0x636326f93a16be14b36b7e62c546370d81d285d1f5398e13d5348fa03a00d05.json