# We need to know where the dependencies live
- "@openzeppelin=./node_modules/@openzeppelin"
# Sometimes you want to enforce a speecific solidity version
# 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"
# This parameter tells the fuzzer to also fuzz these contracts
additional_contracts_addresses:
- "0x0eb775F99A28cb591Fa449ca74eF8E7cEd3A609a"
- "0x21C62e9c9Fcb6622602eBae83b41abb6b28d7256"
# We'll do fuzzing with 32 cores π
# When the campaign is created it'll get a name <prefix>_<random_characters>
campaign_name_prefix: "my-first-campaign"
# Set a default project to which your campaigns will be attached to
project: "my project name"
# Set the API key, which can be obtained from the Diligence Fuzzing Dashboard
# Point to your ganache node which holds the seed π±
rpc_url: "http://localhost:8545"
# Set a time limit, at the end of which the campaign is stopped, e.g. 10minutes , 2hours, 3days
# 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 π)