Operations on Solo

Using Solo with Mirror Node

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

Overview

The Hiero Mirror Node stores the full transaction history of your local Solo network and exposes it through several interfaces:

A web-based block explorer (Hiero Mirror Node Explorer) at http://localhost:8080.
A REST API via the mirror-ingress service at http://localhost:8081 (recommended entry point-routes to the correct REST implementation).
A gRPC endpoint for mirror node subscriptions.

This guide walks you through adding Mirror Node and the Hiero Explorer to a Solo network, and shows you how to query transaction data and create accounts.

Managing Your Network

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

Overview

This guide covers day-to-day management operations for a running Solo network, including starting, stopping, and restarting nodes, capturing logs, and upgrading the network.

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 deployed using solo one-shot single deploy.

Find Your Deployment Name

Most management commands require your deployment name. Run the following command to retrieve it:

Cleanup

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

Overview

This guide covers how to tear down a Solo network deployment, understand resource usage, and perform a full reset when needed.

Prerequisites

Before proceeding, ensure you have completed the following:

Quickstart — you have a running Solo network deployed using solo one-shot single deploy.

Destroying Your Network

Important: Always destroy your network before deploying a new one to avoid conflicts and errors.

To remove your Solo network:

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:

Troubleshooting

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

This guide covers common issues you may encounter when using Solo and how to resolve them.

Use this page when something is failing and you need to diagnose or recover quickly.

If you are looking for setup or day-to-day usage guidance rather than failure diagnosis, start with these pages:

FAQs

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

One-command deployment options and variants

How can I set up a Solo network in a single command?

You can run one of the following commands depending on your needs:

Single Node Deployment (recommended for development):
```
brew install hiero-ledger/tools/solo
```
For more information on Single Node Deployment, see Quickstart
Multiple Node Deployment (for testing consensus scenarios):
```
solo one-shot multiple deploy --num-consensus-nodes 3
```
For more information on Multiple Node Deployment, see Quickstart

Operations on Solo

Using Solo with Mirror Node

Overview

Managing Your Network

Overview

Prerequisites

Find Your Deployment Name

Cleanup

Overview

Prerequisites

Destroying Your Network

Dynamically add, update, and remove Consensus Nodes

Overview

Prerequisites

Troubleshooting

Quick Navigation

Related Operational Topics

FAQs

One-command deployment options and variants

How can I set up a Solo network in a single command?