Comprehensive Settings Reference
This document provides a complete reference for all Teranode configuration settings, organized by component.
Table of Contents
Overview
All Teranode services accept settings through a centralized Settings object that allows local and remote servers to have their own specific configuration.
For general information on how the configuration system works, see the Settings Overview.
For deployment-specific information, see:
General Configuration
Configuration Files
Settings are stored in two files:
settings.conf: Global settings with sensible defaults for all environmentssettings_local.conf: Developer-specific and deployment-specific overrides (not in source control)
Configuration System
The configuration system uses a layered approach with the following priority:
SETTING_NAME.context_name: Context-specific override (highest priority)SETTING_NAME.base: General overrideSETTING_NAME: Base setting (lowest priority)
Environment Variables
Most settings can be configured via environment variables using the pattern:
TERANODE_<SERVICE>_<SETTING_NAME>
Services
For detailed service-specific configuration documentation, see:
- Alert Service - Bitcoin SV alert system configuration
- Asset Server - HTTP/WebSocket interface configuration
- Block Assembly - Block assembly service configuration
- Blockchain - Blockchain state management configuration
- Block Persister - Block persistence configuration
- Block Validation - Block validation configuration
- Legacy - Legacy Bitcoin protocol compatibility configuration
- P2P - Peer-to-peer networking configuration
- Propagation - Transaction propagation configuration
- RPC - JSON-RPC server configuration
- Subtree Validation - Subtree validation configuration
- UTXO Persister - UTXO set persistence configuration
- Validator - Transaction validation configuration