> ## Documentation Index
> Fetch the complete documentation index at: https://second.tech/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Bark

You can configure `bark` using environment variables, a `config.toml` configuration file, or both.

## Environment variables

Available environment variables:

* `BARK_VERBOSE` (`1` or `true`): set verbose logging
* `BARK_QUIET` (`1` or `true`): set no logging
* `BARK_DATADIR`: set the datadir to use
* `BARK_LOG`: set a `env_logger`-style filter for logging (f.e. `info` or `info,bark=trace`, ...)

<Tip>
  **Default datadir**

  To check your default datadir, run the following command:
</Tip>

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
bark help
```

## Configuration file

Go to your Bark datadir and you should find a `config.toml` file. Here are the available configuration variables:

* `server_address`: the address of your ark server
* `esplora_address`: the address of the Esplora HTTP REST server to use
* `bitcoind_address`: the address of the `bitcoind` RPC server to use
* `bitcoind_cookiefile`: the path to the `bitcoind` rpc cookie file
* `bitcoind_user`: the `bitcoind` RPC username
* `bitcoind_pass`: the `bitcoind` RPC password
* `vtxo_refresh_expiry_threshold`: the number of blocks before expiration to refresh vtxos
* `vtxo_exit_margin`: an upper limit of the number of blocks we expect to need to safely exit the vtxos
* `htlc_recv_claim_delta`: the number of blocks to claim a HTLC-recv VTXO
* `fallback_fee_rate`: a fallback fee rate to use in sat/kWu when we fail to retrieve a fee rate from the configured `bitcoind`/esplora connection
* `round_tx_required_confirmations`: the number of confirmations required before considering a round tx fully confirmed

Check the configuration struct on the bark repository [here](https://gitlab.com/ark-bitcoin/bark/-/blob/master/bark/src/config.rs#L75).