Advanced on Solo

One-shot Falcon Deployment

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

Overview

One-shot Falcon deployment is Solo’s YAML-driven one-shot workflow. It uses the same core deployment pipeline as solo one-shot single deploy, but lets you inject component-specific flags through a single values file.

One-shot use Falcon deployment when you need a repeatable advanced setup, want to check a complete deployment into source control, or need to customise component flags without running every Solo command manually.

Falcon is especially useful for:

Solo CLI Reference

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

Overview

This page is the canonical command reference for the Solo CLI.

Use it to look up command paths, subcommands, and flags.
Use solo <command> --help and solo <command> <subcommand> --help for runtime help on your installed version.
For legacy command mappings, see CLI Migration Reference.

Output Formats (`--output`, `-o`)

Solo supports machine-readable output for version output and for command execution flows that honor the output format flag.

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.

Advanced Solo Setup

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

CLI Migration Reference

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

Overview

Use this page when migrating scripts or runbooks from legacy Solo CLI command paths (< v0.44.0) to the current command structure.

For full current syntax and flags, see Solo CLI Reference.

Legacy to Current Mapping

Legacy command	Current command
`init`	`init`
`block node add`	`block node add`
`block node destroy`	`block node destroy`
`block node upgrade`	`block node upgrade`
`account init`	`ledger system init`
`account update`	`ledger account update`
`account create`	`ledger account create`
`account get`	`ledger account info`
`quick-start single deploy`	`one-shot single deploy`
`quick-start single destroy`	`one-shot single destroy`
`cluster-ref connect`	`cluster-ref config connect`
`cluster-ref disconnect`	`cluster-ref config disconnect`
`cluster-ref list`	`cluster-ref config list`
`cluster-ref info`	`cluster-ref config info`
`cluster-ref setup`	`cluster-ref config setup`
`cluster-ref reset`	`cluster-ref config reset`
`deployment add-cluster`	`deployment cluster attach`
`deployment list`	`deployment config list`
`deployment create`	`deployment config create`
`deployment delete`	`deployment config delete`
`explorer deploy`	`explorer node add`
`explorer destroy`	`explorer node destroy`
`mirror-node deploy`	`mirror node add`
`mirror-node destroy`	`mirror node destroy`
`relay deploy`	`relay node add`
`relay destroy`	`relay node destroy`
`network deploy`	`consensus network deploy`
`network destroy`	`consensus network destroy`
`node keys`	`keys consensus generate`
`node freeze`	`consensus network freeze`
`node upgrade`	`consensus network upgrade`
`node setup`	`consensus node setup`
`node start`	`consensus node start`
`node stop`	`consensus node stop`
`node restart`	`consensus node restart`
`node refresh`	`consensus node refresh`
`node add`	`consensus node add`
`node update`	`consensus node update`
`node delete`	`consensus node destroy`
`node add-prepare`	`consensus dev-node-add prepare`
`node add-submit-transaction`	`consensus dev-node-add submit-transactions`
`node add-execute`	`consensus dev-node-add execute`
`node update-prepare`	`consensus dev-node-update prepare`
`node update-submit-transaction`	`consensus dev-node-update submit-transactions`
`node update-execute`	`consensus dev-node-update execute`
`node upgrade-prepare`	`consensus dev-node-upgrade prepare`
`node upgrade-submit-transaction`	`consensus dev-node-upgrade submit-transactions`
`node upgrade-execute`	`consensus dev-node-upgrade execute`
`node delete-prepare`	`consensus dev-node-delete prepare`
`node delete-submit-transaction`	`consensus dev-node-delete submit-transactions`
`node delete-execute`	`consensus dev-node-delete execute`
`node prepare-upgrade`	`consensus dev-freeze prepare-upgrade`
`node freeze-upgrade`	`consensus dev-freeze freeze-upgrade`
`node logs`	`deployment diagnostics logs`
`node download-generated-files`	No direct equivalent. Use `deployment diagnostics all` or `deployment diagnostics debug` based on intent.
`node states`	`consensus state download`

Notes

Current command tree includes additional commands not present in legacy CLI (for example ledger account predefined, deployment refresh port-forwards, and consensus node collect-jfr).
Legacy mappings are intended for migration support only. Prefer documenting and scripting the current command paths.

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.

Network Deployments

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

Attach JVM Debugger and Retrieve Logs

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

Overview

This guide covers three debugging workflows:

Retrieve logs from a running consensus node using k9s or the Solo CLI
Attach a JVM debugger in IntelliJ IDEA to a running or restarting node
Save and restore network state files to replay scenarios across sessions

Prerequisites

Before proceeding, ensure you have completed the following:

System Readiness — your local environment meets all hardware and software requirements.
Quickstart — you have a running Solo cluster and are familiar with the basic Solo workflow.

You will also need:

Step-by-Step Manual Deployment

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

Overview

Manual deployment lets you deploy each Solo network component individually, giving you full control over configuration, sequencing, and troubleshooting. Use this approach when you need to customise specific steps, debug a component in isolation, or integrate Solo into a bespoke automation pipeline.

Prerequisites

Before proceeding, ensure you have completed the following:

System Readiness — your local environment meets all hardware and software requirements (Docker, kind, kubectl, helm, Solo).

Using Network Load Generator with Solo

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

Using Network Load Generator with Solo

The Network Load Generator (NLG) is a benchmarking tool that stress tests Hiero networks by generating configurable transaction loads. Use it to validate the performance and stability of your Solo network before deploying to production or running integration tests.

Prerequisites

Before proceeding, ensure you have completed the following:

System Readiness — your local environment meets all hardware and software requirements.
Quickstart — you have a running Solo network and are familiar with the basic Solo workflow.

Step 1: Start a Load Test

Use the rapid-fire load start command to install the NLG Helm chart and begin a load test against your deployment.

Customizing Solo with Tasks

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

Overview

The Task tool (task) is a task runner that enables you to deploy and customize Solo networks using infrastructure-as-code patterns. Rather than running individual Solo CLI commands, you can use predefined Taskfile targets to orchestrate complex deployment workflows with a single command.

This guide covers installing the Task tool, understanding available Taskfile targets, and using them to deploy networks with various configurations. It also points to maintained example projects that demonstrate common Solo workflows.

Dynamically add, update, and remove Consensus Nodes

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

Overview

This guide covers how to dynamically manage consensus nodes in a running Solo network - adding new nodes, updating existing ones, and removing nodes that are no longer needed. All three operations can be performed without taking the network offline.

Prerequisites

Before proceeding, ensure you have:

A running Solo network. If you don’t have one, deploy using one of the following methods:
1. Quickstart - single command deployment using solo one-shot single deploy.
2. Manual Deployment - step-by-step deployment with full control over each component.
Set the required environment variables as described below:

Solo CI Workflow

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

Overview

This guide walks you through integrating Solo into a GitHub Actions CI pipeline - covering runner requirements, tool installation, and automated network deployment. Each step installs dependencies directly in the workflow, since CI runners are fresh environments with no pre-installed tools.

Prerequisites

Before proceeding, ensure you have completed the following:

System Readiness — your local environment meets all hardware and software requirements.
Quickstart — you are familiar with the basic Solo workflow and the solo one-shot single deploy command.

This guide assumes you are integrating Solo into a GitHub Actions workflow where each runner is a fresh environment. The steps below install all required tools directly inside the workflow rather than relying on pre-installed dependencies.

CLI Reference

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

Advanced on Solo

One-shot Falcon Deployment

Overview

Solo CLI Reference

Overview

Output Formats (--output, -o)

Using Environment Variables

Overview

General

Network and Node Identity

Operator and Key Configuration

Advanced Solo Setup

CLI Migration Reference

Overview

Legacy to Current Mapping

Notes

Falcon Values File Reference

Overview

Network Deployments

Attach JVM Debugger and Retrieve Logs

Overview

Prerequisites

Step-by-Step Manual Deployment

Overview

Prerequisites

Using Network Load Generator with Solo

Using Network Load Generator with Solo

Prerequisites

Step 1: Start a Load Test

Customizing Solo with Tasks

Overview

Dynamically add, update, and remove Consensus Nodes

Overview

Prerequisites

Solo CI Workflow

Overview

Prerequisites

CLI Reference

Output Formats (`--output`, `-o`)