How to Set Up a Cardano Stake Pool: A Complete Guide for 2026
Everything you need to go from bare metal to producing blocks on Cardano mainnet.
What Is a Cardano Stake Pool?
A Cardano stake pool is a network node responsible for processing transactions and producing new blocks. Unlike proof-of-work systems, Cardano uses Ouroboros — a proof-of-stake consensus protocol where the probability of producing a block is proportional to the ADA delegated to your pool.
A production stake pool setup consists of three components:
- Block Producer (BP) — the core node that creates blocks and holds your operational keys. This machine should never be publicly accessible.
- Relay Nodes (2+ recommended) — public-facing nodes that connect to the wider Cardano network and route transactions to your block producer.
- Air-Gapped Offline Machine — used exclusively for signing with cold keys. This machine should never touch the internet.
Hardware Requirements
Each node needs at minimum an Intel/AMD x86 processor with 2+ cores at 2GHz+, 24 GB RAM, 150 GB free storage (250 GB recommended), a static IP with 10 Mbps+ broadband, and 64-bit Linux (Ubuntu 22.04 LTS recommended). Expect roughly 1 GB/hour of bandwidth.
In total, you'll need: 1 block producer server, at least 2 relay servers (ideally in different regions), 1 air-gapped machine, approximately 505 ADA minimum (500 refundable pool deposit + fees), and ADA for your pledge.
For a production pool you intend to run long-term, target 4+ cores, 24 GB+ RAM, 350 GB+ SSD, and 100 Mbps+ connections. Popular hosting providers among SPOs include Hetzner, OVH, DigitalOcean, AWS, and Contabo. You can check which providers host most relays at cexplorer.io/relays. Consider servers in 2+ physical locations for redundancy.
Step-by-Step Setup
We recommend the Guild Operators toolset for most new SPOs. It provides guild-deploy.sh for installation and CNTools — an interactive menu for managing your pool. This is the method we use at QBT Labs for client deployments.
Other excellent references: the CoinCashew guide, the Cardano Developer Portal, and @ItsDave_ADA's SPO walkthrough.
Phase 1: Server Provisioning & Hardening
Provision your servers, install Ubuntu 22.04 LTS, and harden each one:
- Disable root login, set up SSH key-based authentication, disable password auth
- Configure UFW firewall: relays allow port 6000 from anywhere + SSH from your IP; block producer allows port 6000 only from relay IPs + SSH from your IP
- Install and configure
fail2banfor brute force protection - Enable automatic security updates
- Run cardano-node as a dedicated non-root user
Phase 2: Install Cardano Node
On each server, use the Guild Operators deployment script:
mkdir "$HOME/tmp" && cd "$HOME/tmp" curl -sS -o guild-deploy.sh https://raw.githubusercontent.com/cardano-community/guild-operators/master/scripts/cnode-helper-scripts/guild-deploy.sh chmod 755 guild-deploy.sh ./guild-deploy.sh
The script handles dependencies, downloads the correct cardano-node binary (currently 10.5.1 as of January 2026), and sets up the directory structure.
Phase 3: Sync the Blockchain
Start the node and let it sync. A full sync from genesis can take 12-24+ hours, but Mithril snapshots let you bootstrap the blockchain state in minutes using cryptographically verified snapshots. This is now the standard approach for new deployments — Guild Operators includes Mithril integration.
Phase 4: Generate Keys on the Air-Gapped Machine
This is the most security-critical phase. All key generation happens on your air-gapped offline machine — a computer that has never been connected to the internet.
The key hierarchy:
- Cold key pair — your pool's master key. NEVER put this on an online server.
- VRF key pair — used for the slot leader lottery.
- KES key pair — Key Evolving Signature keys that sign blocks. These rotate every ~62 days.
- Operational certificate — signed by your cold key, authorizes the KES key for a specific period.
Transfer to the block producer via USB: KES signing key, VRF signing key, operational certificate, and pool node counter. Keep offline: cold signing key and cold verification key.
CNTools makes this process interactive and harder to mess up — it walks you through each step with a menu-driven interface. See the offline workflow guide for the full process.
Phase 5: Configure P2P Topology
Cardano now uses P2P networking, replacing the legacy topology updater. Configure your block producer to connect only to your relay nodes. Configure relays to connect to your block producer and discover other public relays via P2P. Your relays advertise themselves to the network; your block producer stays hidden.
Phase 6: Register Your Stake Pool
With your node synced and keys generated, register on-chain. Your pool registration certificate includes:
- Pledge amount — ADA you commit from your own wallet
- Fixed cost — minimum 340 ADA per epoch (protocol enforced)
- Margin — your percentage cut of rewards above the fixed cost
- Metadata URL — pointing to a JSON file with your pool's name, description, ticker (3-5 uppercase characters), and homepage
- Relay information — DNS names or IPs of your relay nodes
{ "name": "Your Pool Name", "description": "A brief description of your pool", "ticker": "TICK", "homepage": "https://yourpool.com" }
The metadata file must be under 512 bytes. Host it on GitHub Pages, your own domain, or IPFS. Registration costs approximately 5 ADA in fees plus the 500 ADA pool deposit (refundable upon deregistration).
Your pool becomes active and eligible for block production 2 epochs (~10 days) after submission. CNTools handles the registration transaction interactively.
Monitoring Your Pool
Once live, monitoring is critical. Missed blocks mean missed rewards.
gLiveView provides a terminal-based real-time dashboard showing sync status, peer connections, and block height. Grafana + Prometheus gives you the full monitoring stack with pre-built dashboards from Guild Operators. CNCLI checks your block production schedule and validates produced blocks. External tools like PoolTool.io, Cardanoscan.io, and ADApools.org provide public visibility and historical data.
Set up alerts for: node falling behind chain tip, missed block production slots, KES key approaching expiry, disk space running low, and abnormal resource usage.
Common Gotchas
KES key rotation — your KES keys expire after ~62 days. If you don't rotate them, your pool stops producing blocks with no warning. Set a calendar reminder and automate the alert.
Metadata hash mismatch — the hash of your metadata file must match exactly what's registered on-chain. If you update the file (even adding a space), you must re-register with the new hash.
Block producer exposure — your block producer should never accept connections from the public internet. Only your own relay nodes.
Pledge availability — your pledged ADA must be present in the pledge wallet at epoch boundary snapshot time. If you move it, even temporarily, your pool produces blocks with reduced or zero rewards for that epoch.
Epoch boundary timing — pool registrations, pledge changes, and parameter updates take effect 2 epochs after submission (~10 days). Plan accordingly.
Is Running a Stake Pool Worth It?
Economically, a Cardano stake pool needs significant delegation — typically 1M+ ADA — to consistently produce blocks and generate meaningful rewards. The ecosystem is competitive with over 3,000 registered pools.
But the value isn't purely financial. Running a stake pool gives you deep understanding of Cardano's consensus mechanism, infrastructure expertise that transfers to other networks, a direct role in securing and decentralizing the network, and a foundation for building other Cardano-based services.
Need Help Setting Up?
Setting up a production-grade stake pool with hardened security, proper key management, monitoring, and ongoing maintenance takes time and expertise. Many teams would rather focus on their core project.
QBT Labs offers professional stake pool setup from €1,500 — including full server provisioning, node installation, air-gapped key generation, mainnet registration, monitoring setup, documentation, and 30 days of post-setup support.
We've built and operated node infrastructure across Cardano, Ethereum, Solana, Sui, and more. Node ops is what we do.
Visit qbtlabs.io or email [email protected] to get started.
Resources & Links
Setup Guides:
- Guild Operators Documentation — the toolkit we recommend
- CoinCashew SPO Guide — the most comprehensive community guide
- Cardano Developer Portal — Operate a Stake Pool — official documentation
- Dave's SPO Journey — practical walkthrough by @ItsDave_ADA
- Cardano Hardware Requirements — official minimum specs
Key Tools:
- CNTools — interactive pool management
- gLiveView — real-time terminal dashboard
- CNCLI — block schedule checker & validator
- Mithril — fast blockchain bootstrapping via snapshots
- cardano-cli — official Cardano command line interface
Monitoring & Explorers:
- PoolTool.io — pool performance monitoring
- Cardanoscan.io — blockchain explorer
- ADApools.org — pool statistics & rankings
- cexplorer.io — relay distribution & network stats
Community:
- Cardano SPO Telegram — stake pool operator community
- Cardano Forum — Staking — discussions and support
- Guild Operators Support — CNTools and guild-deploy help
Related Reading
- Validator Node Operations: Security Best Practices — How to secure the stake pool you just set up
- Building High-Performance Cardano Indexers — Building data infrastructure on top of your Cardano node
QBT Labs builds professional blockchain infrastructure and provides market making services across multiple CEXs and DEXs. Based in Cyprus, serving Web3 teams globally.
Related Articles
AMP Deep Dive: Channel State, Settlement, and Security
How does channel state actually work on different chains? What makes AMP settlement secure? A technical deep dive for builders.
Building High-Performance Cardano Indexers
How we achieved a 58x speedup — from 33 blocks/min to 1,916 blocks/min — by rethinking everything about our indexing pipeline.
Validator Node Operations: Security Best Practices
How we secure Cardano stake pools in production — from air-gapped key management to relay architecture — and how it compares to what the pros do across chains.