Use a profile file
You can load TOML configuration files containing custom settings for specific user profiles using
the --profile CLI option.
For example:
besu --config-file=config.toml --profile=staker
In this example, config.toml is the user-provided configuration file, and staker is
the pre-configured profile containing custom settings.
Any configuration options explicitly set in the configuration file or command line will overwrite the same options set in the profile file. See the configuration order of precedence for more information.
You can use the following profiles:
Minimalist staker profile
For stakers who want to maximize their hardware value but don't want to serve full sets of data to their peers, Besu provides a minimalist staker profile. See the minimalist staker profile file for the custom settings.
To use the minimalist staker profile, run Besu with
--profile set to minimalist_staker:
besu --profile=minimalist_staker
Staker profile
For stakers who want to maximize their hardware value and also want to serve full sets of data to their peers, Besu providers a staker profile. See the staker profile file for the custom settings.
To use the staker profile, run Besu with --profile set to staker:
besu --profile=staker
Enterprise/Private profile
For private network operators who want to minimize confusion by setting sensible defaults, Besu provides an enterprise/private profile. This profile is designed to handle specific use cases for private network operators. See the enterprise/private profile file for the custom settings.
To use the enterprise/private profile, run Besu with
--profile set to enterprise or private:
besu --profile=staker
or
besu --profile=private
enterprise and private are aliases for the same profile.