Node Configuration File Reference and Parameter Changes

The Algorand node configuration file (config.json) is the primary interface for operators to control the behavior of algod and other node software. This reference tracks the lifecycle of every parameter, including logging directives, telemetry settings, and network configurations. A mismatch between a node's configuration and its software version is a leading cause of startup failures, degraded performance, and unintended exposure of telemetry data. Operators must treat the configuration file as a versioned artifact that requires the same rigorous change control as the node binaries themselves.

Parameter changes are introduced through new software releases and are documented in the release notes for algod, but the operational impact is often underappreciated. A new default value can alter a node's catchup behavior or its resource consumption. A deprecated flag, if not removed from a configuration file, can cause a node to fail to start after an upgrade. This reference explicitly maps each parameter to its introduction and deprecation version, allowing infrastructure teams to audit their configurations against their target release before an upgrade, rather than diagnosing failures in production.

For exchanges, custodians, and validators running high-availability node fleets, configuration drift is a systemic risk. A single misconfigured telemetry endpoint can leak sensitive operational data, while an incorrect archival setting can lead to silent data loss. Chainscore Labs helps operators build automated configuration validation pipelines that compare running configurations against a versioned, secure baseline, ensuring that every node in a fleet is compliant before and after every upgrade.

The Algorand node configuration file (config.json) is the single source of truth that governs the operational behavior of participation and relay nodes. It controls critical functions including network identity, telemetry reporting, logging verbosity, catchup behavior, and the archival mode toggle. Unlike consensus protocol rules, which are enforced by the network, these parameters are set locally by each operator. A misconfigured node can fail to start, silently drop participation, or expose sensitive telemetry data, making the configuration file a primary operational risk surface for validators, exchanges, and infrastructure providers.

The parameter lifecycle is tied directly to the algod release cadence. Each new software version can introduce new configuration keys, alter the default values of existing parameters, or deprecate and eventually remove obsolete flags. For example, a release may change the default for EnableCatchupFromArchiveServers or introduce a new telemetry endpoint that is opt-out rather than opt-in. Operators who apply a software upgrade without auditing the accompanying configuration changes risk startup failures, where the node refuses to initialize due to an unrecognized or conflicting parameter, or silent behavioral shifts that degrade performance or leak data. The absence of a formal, machine-readable changelog for config.json means that operators must manually diff the template file shipped with each release against their production configuration.

A robust configuration management practice involves treating config.json as a controlled artifact within a change management pipeline. Operators should maintain a canonical production configuration, diff it against the new release's template before each upgrade, and explicitly decide whether to adopt new defaults or preserve existing behavior. Parameters that are deprecated should be scheduled for removal in a subsequent maintenance window to prevent future startup failures. For large-scale deployments, such as exchanges and custodians running multi-node fleets, configuration drift between nodes can create inconsistent participation behavior and complicate incident response. Chainscore Labs can audit production configurations for compatibility with target releases, identify security-sensitive telemetry or logging settings, and build automated validation pipelines that prevent misconfigurations from reaching production nodes.