Run a node

This page summarises how to run a Logos node on the public Testnet. It follows the official guide. Use the official docs for the exact commands, because versions and bootstrap peers change between releases.

Which version this covers

The official guide at docs.logos.co/run-a-node says it is accurate for Testnet v0.3. It pins these packages:

• logosctl 0.3.2 (the command-line tool that starts and controls the node)
• blockchain_module 0.3.1
• storage_module 3.0.2
• delivery_module 0.3.2

The docs note that package versions are pinned on their own and need not match the testnet number. Check the version box at the top of each docs page before you start.

Choose a route

• Full node from the command line. Runs blockchain, storage and delivery together on a Linux server. Guide: Run a Logos node with blockchain, storage, and delivery.
• Blockchain node only, from the command line. Guide: Run a Logos Blockchain node on the public testnet from the CLI. This page says it is accurate for Testnet v0.3.0 and installs blockchain_module 0.3.0. It supports Linux x86_64, recent macOS on Apple silicon, and Raspberry Pi 5.
• Blockchain node from Basecamp. Guide: Run a Logos Blockchain node from Basecamp. On 9 October 2026 the node programme page said this guide still covers Testnet v0.2.1. See Basecamp.

What you need

For the full node, the official guide asks for:

• a Linux host with a public IPv4 address
• root or sudo access
• ports 3000/udp, 8090/udp, 8091/tcp, 9000/udp, 30303/tcp and 30303/udp open on the firewall, and forwarded if you are behind NAT
• a CPU with 2 cores at 2 GHz. On x86_64 it must support the ADX instruction. Generic virtual machine CPU models such as kvm64 and qemu64 hide ADX and make the blockchain module crash.
• 1 GB of RAM
• 1 to 2 GB free on an SSD for testnet use
• a reliable connection with about 1 Mbps of free bandwidth

To take part in the Blend Network you also need a stable external IP address and a low-latency connection. The docs recommend 10 Mbps or more.

Steps

These steps follow the full-node guide. The guide has the commands.

1. Install logosctl. Download the logosctl 0.3.2 release archive. Check its SHA-256 digest, extract it and install it as /usr/local/bin/logosctl.
2. Prepare the host. Create a logos system user and the data directory /var/lib/logos-node. Open the ports listed above.
3. Install the modules. As the logos user, start the daemon, refresh the module catalogue and install the three pinned modules by their root hashes. Installing a module does not load it.
4. Start the node. Run logosctl daemon start in one terminal. Use a second terminal for module commands.
5. Start the blockchain module. The 0.3.1 blockchain module starts a new chain with a new genesis, so the state directory must be empty. Balances and Blend declarations from the old chain do not carry over. Write the bootstrap peer file, load the module and generate user_config.yaml and keystore.yaml. Restrict both files to your user and never publish user_config.yaml.
6. Fund the node by mining. Once the node reports Online, start proof-of-work mining. Rewards are claimed to your node's key automatically. Mining is off by default and stops on restart, so start it again after each restart.
7. Join the Blend Network (optional). Fund the Blend keys from your keystore by mining, then follow the Blend guide linked from the docs.
8. Check storage. With logosctl 0.3.2 the storage module starts automatically. Check that it is running before you download anything.
9. Start delivery. Configure and start the delivery module. Delivery enables QUIC by default, so port 30303 must be open for both TCP and UDP.
10. Check the node is healthy. Query the daemon, list the loaded modules, check the bound ports and check the blockchain sync state.
11. Run unattended (optional). The guide gives a systemd service for the node and a separate start-up script for the modules.

The docs warn against calling pow_status or pow_claimable_rewards before the node is Online. While the node is bootstrapping these calls never return, and later blockchain commands fail until you restart the daemon.

Bootstrap nodes for the 0.3.0 genesis

On 9 October 2026 a forum thread asked operators to join the Logos 0.3.0 genesis as bootstrap nodes. It has three steps:

1. With the module installed and the daemon running, load blockchain_module and call generate_user_config. This writes user_config.yaml and keystore.yaml.
2. Find the stake public key in keystore.yaml and post it as a reply in the thread.
3. Back up keystore.yaml. The genesis stake is assigned to that key and the module will not generate a second keystore in the same place. The post warns: "Lose the file, lose the stake."

Read the thread before you post.

Earlier versions

The roadmap keeps a Testnet v0.2.1 node operator guide, dated 7 September 2026. It pins older packages and is kept for reference. Use the docs for the current release.

See also

• Testnet
• Basecamp
• Getting started
• FAQ
• Logos
• Running a Logos node, in Start a Circle

Sources

• Run a Logos node with blockchain, storage, and delivery, Logos documentation, Testnet v0.3
• Run a Logos Blockchain node on the public testnet from the CLI, Logos documentation, Testnet v0.3.0
• Join the Logos 0.3.0 genesis as a bootstrap node, Logos Forum, 9 October 2026
• Testnet version 0.3: release notes, Logos roadmap
• Testnet version 0.2.1: Node Operator Guide, Logos roadmap, 7 September 2026
• Node Programme, logos.co, read 9 October 2026

Page status: Usable. Stub · Outline · Usable · Guide · Star. Anyone can improve this page and change its status.