CLI Usage

Overview
Scribble accepts normal Solidity files and has 3 output modes:
1.In flat mode, all the dependencies of the target Solidity file(s) are bunched up and emitted as one giant blob of Solidity. This is useful for submitting the instrumented code to services like ` MythX.
2.In files mode, for each file foo.sol containing contracts with scribble annotations, Scribble emits a foo.instrumented.sol in the same directory and leaves the original unchanged. Note that scribble may instrument files that are not specified on the command line, but are reachable by a chain of imports.
3.In json mode, Scribble behaves similarly to flat mode, in that it first flattens all the files necessary to compile the target into one flat Solidity blob. Afterwards, it runs solc on that flat solidity blob and outputs the slightly modified standard JSON output of the used compiler version.
Quick recipes
We provide examples for the most common use cases. For all examples assume we have the following 2 solidity files in the current directory:
Base.sol
1
contract Base {
2
}
Copied!
Foo.sol
1
import "Base.sol";
2
contract Foo is Base {
3
    /// #if_succeeds {:msg "P1"} y == x + 1; 
4
    function inc(uint x) public pure returns (uint y) {
5
        return x+1;
6
    }
7
}
Copied!
Emitting a flat instrumented file
If we want to instrument Foo.sol (and any required imports) and emit it all into a single Foo.flat.sol we can run:
1
scribble Foo.sol --output-mode flat --output Foo.flat.sol
Copied!
Note that both the input and the output can be -- which would make Scribble work with stdin/stdout. The below command uses stdin/stdout to do the same thing as the previous command:
1
cat Foo.sol | scribble -- --output-mode flat --output -- > Foo.flat.sol
Copied!
Instrumenting files in-place
The files mode is more involved and is intended for interoperability with various user testing and deployment environments. To instrument Foo.sol and Base.sol in-place we run:
1
scribble Foo.sol --output-mode files
Copied!
After running this we will have 2 new files in the directory - Foo.instrumented.sol and __scribble_ReentrancyUtils.sol. Foo.instrumented.sol is the instrumented version of Foo.sol, and __scribble_ReentrancyUtils.sol contains a helper contract.
Note that the instrumented Foo.instrumented.sol still imports the original Base.sol. To actually use the instrumented files in this mode, you have to swap them with the originals, before compiling/testing/deploying. You can do so manually, or automatically with the the --arm and --disarm options to scribble (more details here).
Emitting an instrumented JSON artifact
Emitting an instrumented JSON artifact is almost the same as running in flat-mode:
1
scribble Foo.sol --output-mode json --output Foo.flat.json
Copied!
The generated Foo.flat.json contains the compiled version of the flattened instrumented solidity, along with some extra info. (For more details see  this section).
Command line options reference
1
Scribble
2
​
3
  A Solidity runtime verification tool for property based testing. 
4
​
5
Options
6
​
7
  -h, --help                               Print help message                                                            
8
  -v, --version                            Print package version                                                         
9
  -q, --quiet                              Don't output anything to stderr                                               
10
  -i, --input-mode string                  Input mode. Either 'source' or 'json'. When 'source' is specified, input      
11
                                           assumed to be a raw Solidity source code. When 'json' is specified, input     
12
                                           assumed to be a Solc output JSON artifact.                                    
13
  -m, --output-mode string                 Output mode. Either 'flat', 'files' or 'json'. When 'flat' is specified,      
14
                                           output all instrumented contracts toghether. When 'files' is specified, for   
15
                                           every file Foo.sol that contains an annotated contract emit a                 
16
                                           Foo.sol.instrumetned with the instrumented contract. When 'json' is           
17
                                           specified, a JSON object including the original sources, the flattened        
18
                                           bytecode, and a map from property IDs to their locations.                     
19
  -k, --keep-instrumented                  Keep instrumented files after disarming.                                      
20
  -o, --output string                      When the output mode if 'flat' or 'json' specifies where to dump the          
21
                                           flattened contracts. Either a path to a file, or '--' for stdout.             
22
  --utils-output-path string               Path to a folder where the ReentrancyUtils.sol contract should be emitted.    
23
                                           This option is required with '--mode files' and ignore otherwise.             
24
  --instrumentation-metadata-file string   If specified, output instrumentation metadata (src-to-src maps, property      
25
                                           maps) to the specified file.                                                  
26
  --macro-path string                      Path to look for a macro definition file. If path is a directory, then it     
27
                                           would be recusively scanned for macro files.                                  
28
  --path-remapping string                  Path remapping input for Solc. A semicolon separate list of remappings        
29
                                           'prefix=target'                                                               
30
  --compiler-version string                If given, specifies the exact compiler version to use                         
31
  --compiler-kind string                   If given, specifies the type of Solidity compiler to use. Supported values    
32
                                           are 'wasm' and 'native'. Default value is 'native' (can be configured via     
33
                                           environment variable SCRIBBLE_DEFAULT_COMPILER_KIND).                         
34
  --compiler-settings string               If given, specifies additional settings to pass to the underlying compiler as 
35
                                           a JSON string. (e.g. --compiler-settings '{"optimizer:": {"enabled":          
36
                                           true}}'). For more info see https://docs.soliditylang.org/en/latest/using-    
37
                                           the-compiler.html#input-description                                           
38
  --no-assert                              If specified execution will not halt when an invariant is violated (only an   
39
                                           event will be emitted).                                                       
40
  --filter-type string                     If specified instrumentation will happen only for annotations, whose types    
41
                                           are matching supplied regular expression.                                     
42
  --filter-message string                  If specified instrumentation will happen only for annotations, whose messages 
43
                                           are matching supplied regular expression.                                     
44
  --arm                                    When instrumenting files in-place ('--output-mode files') also swap the       
45
                                           instrumented files with the original.                                         
46
  --disarm                                 Find all dependencies of the target that have been swapped with their         
47
                                           instrumented version (all foo.sol s.t. there is a foo.sol.instrumented and    
48
                                           foo.sol.original) and swap them back for the original.                        
49
  --debug-events                           When specified for every failure an additional debug event with values of     
50
                                           variables in the failing predicate is emitted.                                
51
  --user-assert-mode string                Describe how scribble signals user assertion failures to Myhtril/Harvey. Must 
52
                                           be either 'log' or 'mstore'. See wiki for more details.                       
53
  --cov-assertions                         When specified emit an extra user-assertion for each property whenever its    
54
                                           reached. This allows an easy (albeit noisy) way to check which propterties    
55
                                           were reached.                                                                 
56
  --solFiles string[]                      List of solidity files to instrument. Either a list of paths to files, or     
57
                                           '--' for stdin. 
Copied!
Important caveats
1.--output option doesn't have any effect with --output-mode files.
2.--utils-output-path allows to specify a different directory for the __scribble_ReentrancyUtils.sol file. It only works with --output-mode files. It doesn't have any effect with --output-mode flat.
3.If --no-assert is omitted, then there is an assert(false) emitted in the instrumented code every time an invariant is violated. For longer-running fuzzing campaigns, it may be useful to keep running the code even after a property is violated. In those cases only an AssertionFailed(string) event is emitted, which can be caught by tools such as Dili-Faas/MythX/Mythril/Harvey.
4.You will get an error if you pass standard json with missing sources to scribble. Scribble needs the source code to fill in missing information in the AST in certain compiler versions.
5.With the --compiler-kind option you have the choice between using a binary compiler (native) or a WASM based compiler (wasm). If a binary compiler is not available for your environment (e.g. M1 Macs) please use `--compiler-kind wasm`.
6.When instrumenting in-place (i.e. with the option --output-mode files --arm) scribble will always emit an instrumentation metadata file. By default this is placed in the root of the current project tree. The root is defined as the closest directory with a node_modules/ folder in it. If a root folder is not detected, scribble will throw an error requiring you to supply a location for the metadata with the `--instrumentation-metadata-file` option.
Tool - Previous
Installation
Arm and disarm
Last modified 2mo ago
Copy link
Contents
Overview
Quick recipes
Emitting a flat instrumented file
Instrumenting files in-place
Emitting an instrumented JSON artifact
Command line options reference
Important caveats