Operate

Operate covers running a Stable node: full or archive, testnet or mainnet, from install through monitoring. For the chain-level behavior your node enforces (fee model, finality, USDT0 as gas), see Gas pricing, Finality, and the Architecture overview.

Quick links

• System Requirements - Hardware and software requirements for different node types
• Installation Guide - Step-by-step installation instructions for various platforms
• Configuration - Detailed configuration options and best practices
• Snapshots & Sync - Fast sync options using snapshots
• Create a validator - Register a synced node as a validator and self-delegate
• Upgrade Guide - Node upgrade procedures and version history
• Monitoring - Tools and metrics for node monitoring
• Troubleshooting - Common issues and solutions

To read validator data (stake, uptime, voting history) from the chain instead of running stabled, see Index validator data.

Node types

Full node

A full node maintains a complete copy of the blockchain and validates all transactions and blocks. Full nodes:

• Verify all transactions and blocks
• Maintain the entire blockchain history
• Can serve data to other nodes
• Support the network's decentralization

Archive node

An archive node stores the complete history of all states and can serve historical queries. Archive nodes:

• Store all historical states
• Support historical queries at any block height
• Require significantly more storage
• Essential for block explorers and analytics

Network information

For complete network details including RPC endpoints, block explorers, and chain parameters, see:

• Mainnet - Mainnet details
• Testnet - Testnet details

Support and community

• Discord: Join the Stable Discord

Quick start

For experienced operators who want to get started quickly:

1. Check System Requirements
2. Follow the Installation Guide
3. Configure your node using Configuration Guide
4. Speed up sync with Snapshots
5. Monitor your node with Monitoring Guide

For network parameters and RPC endpoints, see Mainnet Information or Testnet Information.

How node ops connect to the chain

Running a node means enforcing Stable's chain-level rules. These pages explain the behavior your node implements:

• Contracts overview covers the fee model, JSON-RPC surface, and system modules your node serves.
• Finality explains single-slot finality and what "confirmed" means at the consensus layer.
• Architecture overview walks through consensus, execution, database, and RPC layers.
• Gas pricing explains how USDT0-denominated fees are priced and collected.