Using Environment Variables

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Solo supports a set of environment variables that let you customize its behaviour without modifying command-line flags on every run. Variables set in your shell environment take effect automatically for all subsequent Solo commands.

Tip: Add frequently used variables to your shell profile (e.g. ~/.zshrc or ~/.bashrc) to persist them across sessions.

General

Environment Variable	Description	Default Value
`SOLO_HOME`	Path to the Solo cache and log files	`~/.solo`
`SOLO_CACHE_DIR`	Path to the Solo cache directory	`~/.solo/cache`
`SOLO_LOG_LEVEL`	Logging level for Solo operations. Accepted values: `trace`, `debug`, `info`, `warn`, `error`	`info`
`SOLO_DEV_OUTPUT`	Treat all commands as if the `--dev` flag were specified	`false`
`SOLO_CHAIN_ID`	Chain ID of the Solo network	`298`
`FORCE_PODMAN`	Force the use of Podman as the container engine when creating a new local cluster. Accepted values: `true`, `false`	`false`

Network and Node Identity

Environment Variable	Description	Default Value
`DEFAULT_START_ID_NUMBER`	First node account ID of the Solo test network	`0.0.3`
`SOLO_NODE_INTERNAL_GOSSIP_PORT`	Internal gossip port used by the Hiero network	`50111`
`SOLO_NODE_EXTERNAL_GOSSIP_PORT`	External gossip port used by the Hiero network	`50111`
`SOLO_NODE_DEFAULT_STAKE_AMOUNT`	Default stake amount for a node	`500`
`GRPC_PORT`	gRPC port used for local node communication	`50211`
`LOCAL_NODE_START_PORT`	Local node start port for the Solo network	`30212`
`SOLO_CHAIN_ID`	Chain ID of the Solo network	`298`

Operator and Key Configuration

Environment Variable	Description	Default Value
`SOLO_OPERATOR_ID`	Operator account ID for the Solo network	`0.0.2`
`SOLO_OPERATOR_KEY`	Operator private key for the Solo network	`302e020100...`
`SOLO_OPERATOR_PUBLIC_KEY`	Operator public key for the Solo network	`302a300506...`
`FREEZE_ADMIN_ACCOUNT`	Freeze admin account ID for the Solo network	`0.0.58`
`GENESIS_KEY`	Genesis private key for the Solo network	`302e020100...`

Note: Full key values are omitted above for readability. Refer to the source defaults for complete key strings.

Falcon Values File Reference

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This page catalogs the Solo CLI flags accepted under each top-level section of a Falcon values file. Each entry corresponds to the command-line flag that the underlying Solo subcommand accepts.

Sections map to subcommands as follows:

Section	Solo subcommand
`network`	`solo consensus network deploy`
`setup`	`solo consensus node setup`
`consensusNode`	`solo consensus node start`
`mirrorNode`	`solo mirror node add`
`explorerNode`	`solo explorer node add`
`relayNode`	`solo relay node add`
`blockNode`	`solo block node add`

All flag names must be written in long form with double dashes (for example, --release-tag). Flags left empty ("") or matching their default value are ignored by Solo at argument expansion time.

Configuration on Solo

Using Environment Variables

Overview

General

Network and Node Identity

Operator and Key Configuration

Falcon Values File Reference

Overview