---
sidebar_label: Configuration options
sidebar_position: 2
description: Besu private network configuration options reference
keywords: [configuration, options, command line, command line interface, CLI]
---

> For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any documentation URL to get the markdown source.


import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# Private network configuration options

This reference describes the syntax of the Besu private network configuration options.

:::caution Important

This reference contains options that apply to only private networks. For options that apply to both private and public networks, see the [public network options reference](../../public-networks/reference/options.md).

:::

You can specify options:

- On the command line.
  Options are part of the command line interface (CLI); run `besu --help` to display all options and [subcommands](subcommands.md).

- As an environment variable.

- In a [configuration file](../../public-networks/how-to/configure-besu/index.md).

If you specify an option in more than one place, the order of priority is command line, environment variable, configuration file.

If using Bash or Z shell, you can view option suggestions by entering `--` and pressing the Tab key twice.

```bash
besu --Tab+Tab
```

:::warning

Characters such as smart quotes and long (em) hyphens don't work in Besu command line options. Ensure quotes aren't automatically converted to smart quotes, or double hyphens combined into em hyphens.

:::

---

## `permissions-accounts-config-file`

<Tabs>

<TabItem value="Command line example">

```bash
--permissions-accounts-config-file=/home/me/me_configFiles/myPermissionsFile
```

</TabItem>

<TabItem value="Environment variable example">

```bash
BESU_PERMISSIONS_ACCOUNTS_CONFIG_FILE=/home/me/me_configFiles/myPermissionsFile
```

</TabItem>

<TabItem value="Config file example">

```bash
permissions-accounts-config-file="/home/me/me_configFiles/myPermissionsFile"
```

</TabItem>

</Tabs>

The [accounts permissions configuration file]. The default is the `permissions_config.toml` file in the [data directory](../../public-networks/reference/options.md#data-path).

:::tip

`--permissions-accounts-config-file` and [`--permissions-nodes-config-file`](#permissions-nodes-config-file) can use the same file.

:::

---

## `permissions-accounts-config-file-enabled`

<Tabs>

<TabItem value="Command line example">

```bash
--permissions-accounts-config-file-enabled=true
```

</TabItem>

<TabItem value="Environment variable example">

```bash
BESU_PERMISSIONS_ACCOUNTS_CONFIG_FILE_ENABLED=true
```

</TabItem>

<TabItem value="Config file example">

```bash
permissions-accounts-config-file-enabled=true
```

</TabItem>

</Tabs>

Enables or disables file-based account level permissions. The default is `false`.

---

## `permissions-nodes-config-file`

<Tabs>

<TabItem value="Command line example">

```bash
--permissions-nodes-config-file=/home/me/me_configFiles/myPermissionsFile
```

</TabItem>

<TabItem value="Environment variable example">

```bash
BESU_PERMISSIONS_NODES_CONFIG_FILE=/home/me/me_configFiles/myPermissionsFile
```

</TabItem>

<TabItem value="Config file example">

```bash
permissions-nodes-config-file="/home/me/me_configFiles/myPermissionsFile"
```

</TabItem>

</Tabs>

The [nodes permissions configuration file]. The default is the `permissions_config.toml` file in the [data directory](../../public-networks/reference/options.md#data-path).

:::tip

`--permissions-nodes-config-file` and [`--permissions-accounts-config-file`](#permissions-accounts-config-file) can use the same file.

:::

---

## `permissions-nodes-config-file-enabled`

<Tabs>

<TabItem value="Command line example">

```bash
--permissions-nodes-config-file-enabled=true
```

</TabItem>

<TabItem value="Environment variable example">

```bash
BESU_PERMISSIONS_NODES_CONFIG_FILE_ENABLED=true
```

</TabItem>

<TabItem value="Config file example">

```bash
permissions-nodes-config-file-enabled=true
```

</TabItem>

</Tabs>

Enables or disables file-based node level permissions. The default is `false`.

---

## `poa-block-txs-selection-max-time`

<Tabs>

<TabItem value="Command line example">

```bash
--poa-block-txs-selection-max-time=80
```

</TabItem>

<TabItem value="Environment variable example">

```bash
BESU_POA_BLOCK_TXS_SELECTION_MAX_TIME=80
```

</TabItem>

<TabItem value="Config file example">

```bash
poa-block-txs-selection-max-time=80
```

</TabItem>

</Tabs>

The maximum time that can be spent selecting transactions to be included in a block,
as a percentage of the fixed block time of the network.
The default is `75`, or 75%.

:::note
This option only applies to proof-of-authority networks.
For proof-of-stake networks, see
[`--block-txs-selection-max-time`](../../public-networks/reference/options.md#block-txs-selection-max-time).
:::

---

## `poa-discovery-retry-bootnodes`

<Tabs>

<TabItem value="Command line example">

```bash
--poa-discovery-retry-bootnodes=true
```

</TabItem>

<TabItem value="Environment variable example">

```bash
BESU_POA_DISCOVERY_RETRY_BOOTNODES=true
```

</TabItem>

<TabItem value="Config file example">

```bash
poa-discovery-retry-bootnodes=true
```

</TabItem>

</Tabs>

When enabled, Besu always uses [bootnodes](../how-to/configure/bootnodes.md) during peer table refresh on Proof of Authority (PoA) networks. When disabled, bootnodes are only used on first startup. If bootnodes are unavailable after startup, the node may not discover new peers until it is restarted. The default is `true`.

:::note
This option only applies to proof of authority (private) networks.
:::

<!-- Links -->

[accounts permissions configuration file]: ../how-to/use-local-permissioning.md#permissions-configuration-file
[nodes permissions configuration file]: ../how-to/use-local-permissioning.md#permissions-configuration-file
[account permissioning]: ../concepts/permissioning.md#account-permissioning