Node Configuration and Maintenance
A node is configured through two files in $HOME/.osmosisd/config/: app.toml (application settings) and config.toml (CometBFT/consensus and networking). This page covers the settings operators most often tune.
Operator verification required
Recommended values for peers, seeds, and minimum gas prices change over time and with the network. Confirm current values before applying. The keys below are stable; the values are illustrative.
app.toml
minimum-gas-pricessets the lowest gas price your node accepts in the mempool. Set it at or above the current network base fee. Example:minimum-gas-prices = "0.025uosmo".pruningcontrols how much historical state is kept. See Sync Options for pruned vs archive.- API and gRPC (
[api],[grpc]) toggle the REST/gRPC endpoints. Enable only what you serve; a validator typically serves none publicly.
config.toml
persistent_peers/seedsdefine who your node connects to.pex,max_num_inbound_peers/max_num_outbound_peerstune peer discovery and connection counts.[consensus]timeouts are network-tuned; do not change them on a validator without reason.
Routine maintenance
- Keep the binary current with network upgrades; see Chain Upgrades and Cosmovisor.
- Monitor disk usage (pruned nodes still grow); see Sync Options.
- Watch node health and performance; see Monitoring and Alerting and Performance and Profiling.