nimbus-eth1/tools/evmstate
jangko 94a94c5b65 implement better hardfork management 2022-12-02 13:51:42 +07:00
..
config.nim enable chronicles runtime filtering of t8n and evmstate tools 2022-11-18 00:56:23 +07:00
config.nims enable chronicles runtime filtering of t8n and evmstate tools 2022-11-18 00:56:23 +07:00
evmstate.nim implement better hardfork management 2022-12-02 13:51:42 +07:00
evmstate_test.nim implement evmstate CLI for evmlab 2022-10-29 12:16:10 +07:00
helpers.nim implement better hardfork management 2022-12-02 13:51:42 +07:00
readme.md enable chronicles runtime filtering of t8n and evmstate tools 2022-11-18 00:56:23 +07:00

readme.md

EVM state test tool

The evmstate tool to execute state test.

Build instructions

There are few options to build evmstate tool like any other nimbus tools.

  1. Use nimble to install dependencies and your system Nim compiler(version <= 1.6.0).
    $> nimble install -y --depsOnly
    $> nim c -d:release tools/evmstate/evmstate
    $> nim c -r -d:release tools/evmstate/evmstate_test
    
  2. Use nimbus shipped Nim compiler and dependencies.
    $> make update
    $> ./env.sh nim c -d:release tools/evmstate/evmstate
    $> ./env.sh nim c -r -d:release tools/evmstate/evmstate_test
    
  3. Use nimbus makefile.
    $> make update
    $> make evmstate
    $> make evmstate_test
    

Command line params

Available command line params

Usage:

evmstate [OPTIONS]... <inputFile>

 <inputFile>         json file contains state test data.

The following options are available:

 --dump              dumps the state after the run [=false].
 --json              output trace logs in machine readable format (json) [=false].
 --debug             output full trace logs [=false].
 --nomemory          disable memory output [=true].
 --nostack           disable stack output [=false].
 --nostorage         disable storage output [=false].
 --noreturndata      enable return data output [=true].
 --fork              choose which fork to be tested.
 --index             if index is unset, all subtest in the fork will be tested [=none(int)].
 --pretty            pretty print the trace result [=false].
 --verbosity         sets the verbosity level [=0].
                        0 = silent, 1 = error, 2 = warn, 3 = info, 4 = debug, 5 = detail.