How to Set Up a Stellar Validator Node: Step-by-Step Guide

Most Stellar guides teach you to use the network. This one is about helpingrun it. A validator is a stellar-core node that participates in consensus — voting on transaction sets every ~5 seconds. More independent validators in well-chosen quorum slices means a more resilient, decentralized network. This guide is inspired by overcat's excellent step-by-step walkthrough on dev.to — we cover the same ground with the key concepts explained.

Prerequisites

A Linux server (Ubuntu LTS is the common choice), 4+ vCPUs, 8+ GB RAM, fast SSD storage, and a static IP with good connectivity. Keep it on reliable infrastructure — a validator that goes dark at the wrong moment hurts its quorum slice's liveness.

1. Install stellar-core

Install from the official Stellar packages (apt repository) or build from source — the dev.to guide uses Ubuntu packages, which is the fastest path:sudo apt install stellar-core. Verify withstellar-core version.

2. Generate your validator seed

Run stellar-core gen-seed to create your node's secret seed and public node ID (G… address). Guard the seed like a private key — it identifies your validator's votes. Set it as NODE_SEED in your config and announce the public key so others can add you to quorum slices.

3. Configure stellar-core.cfg

The critical file. Key settings: NODE_SEED,NODE_IS_VALIDATOR=true, your database (SQLite for small nodes, PostgreSQL for serious ones), UNSAFE_QUORUM=false, history archive settings (CATCHUP_RECENT for recent history only), and — most important — yourQUORUM_SET: the validators you trust.

4. Choose a good quorum slice

Your quorum slice is the list of organizations whose agreement you require. Stellar has no mining and no elected set — every validator picks whom to trust, and consensus emerges from overlapping slices. Best practice: include several independent, well-run validators (SDF nodes plus other established operators like Lobstr, Satoshipay, publicnode). Do not trust a single organization for a majority.

5. Run, sync, monitor

Start the service and watch stellar-core http-command info — the node catchups to the current ledger, then shows state Synced!. Monitor uptime and lag; production validators expose the info endpoint to alerting. Once stable, ask other operators to add your public key to their quorum slices — that is how you actually start securing the network.

Keep learning

overcat's full walkthrough (dev.to) ·What is a validator? ·Stellar Consensus Protocol ·How Proof-of-Agreement works ·Stellar hub ·Stellar Network masterclass

Frequently asked questions