On the first run of the binary, a folder is automatically created next to it resources/ with the entire configuration structure.
resources/
├── presets/ # directory with user presets
│ ├── backrun.toml
│ ├── transaction-spam.toml
│ └── ...
├── system.toml # application system config
└── proxy.txt # list of proxies
Files are created automatically — you don't need to create anything manually.
To edit the files use VSCode with the plugin TOML Reader — it highlights the structure and keys.
system.toml
This is the main application configuration file that sets general settings applied to all strategies. This file exists as a single instance for the entire system.
The user can create an unlimited number of presets, to quickly switch between different strategies. For example:
The preset is chosen when starting the system — the specified file determines with which parameters the bot will operate.
This way you can prepare different arbitrage scenarios for specific conditions.
This file sets common HTTP proxies for the whole system in the format:
Before starting, the system automatically checks all proxies for validity.
Proxies are used in Transaction Processor and are iteratively switched between requests.
Change tracking
The system tracks any changes in real time in the configuration files.
If the user edits:
the file system.toml, or
the active preset with which the application was started,
then the changes are applied automatically — the bot is instantly restarted under the hood, without stopping the main process, and continues operating with the updated parameters.
