# We need to know where the dependencies live
- "@openzeppelin=./node_modules/@openzeppelin"
# Tell the CLI where to find the compiled contracts and compilation artifacts
build_directory: artifacts
# The following address is going to be the main target for the fuzzing campaign
deployed_contract_address: "0x48b8050b4174f7871ce53AaF76BEAcA765037BFf"
# We'll do fuzzing with 4 cores π
# When the campaign is created it'll get a name <prefix>_<random_characters>
campaign_name_prefix: "my-first-campaign"
# Enable this option if you're fuzzing Scribble annotated code
# It'll visualise all the results for the original source code,
# instead of the instrumentation code.
map_to_original_source: true
# Point to your ganache node which holds the seed π±
rpc_url: "http://localhost:8545"
# This is the contract that the campaign will show coverage for, map issues to, etc.
# It's a list of all the relevant contracts (don't worry about dependencies, we'll get those automatically π)