Skip to main content

Use a profile

You can load a profile to extend Besu's default configuration, using the --profile option.

Profiles simplify the process of configuring Besu for common use cases. Besu provides the following pre-configured profiles:

Alternatively, you can customize and load external profiles.

note

Run ./besu --help to view all available profiles.

note

A configuration option specified in the configuration file or on the command line overrides the same option set in the profile.

Minimalist staker profile​

--profile=MINIMALIST_STAKER is optimized for stakers who want to maximize their hardware value but don't want to serve full sets of data to their peers, See the minimalist staker profile on GitHub for the custom settings.

Staker profile​

--profile=STAKER is optimized for stakers who want to maximize their hardware value while also serving full sets of data to their peers. See the staker profile on GitHub for the custom settings.

Enterprise/Private profile​

ENTERPRISE and PRIVATE are aliases for the same profile. --profile=PRIVATE / --profile=ENTERPRISE supports private network operators and enterprises by handling specific use cases that apply to private network operators. See the enterprise/private profile on GitHub for the custom settings.

When using this profile, set --sync-mode=FULL and --data-storage-format=FOREST.

Load external profiles​

You can use external profiles to create custom Besu bundles with various plugins and their default options.

Add external profiles to a profiles directory under the root Besu directory. Run Besu with --profile set to the external profile file name, without the .toml extension. For example, to load the profiles/custom_profile.toml profile, run:

besu --profile=custom_profile
note

You can overwrite the directory in which to place external profiles using the besu.profiles.dir system property.