Node Configuration

Configuring and optimizing node settings

Planned Feature

This feature is planned for future development. Documentation is preliminary.

Overview

This guide covers the configuration options available for ComputeNet nodes, including validators, archive nodes, and gateway nodes.

Planned Documentation

Detailed configuration documentation will be available when node software is released for public testing.

Configuration File

Nodes are configured via a TOML configuration file:

config.toml
# ComputeNet Node Configuration
# Configuration format subject to change

[node]
# Node identifier
name = "my-node"
# Network to connect to
network = "testnet"
# Data directory
data_dir = "/var/lib/computenet"

[network]
# Listen address
listen_addr = "0.0.0.0:30303"
# Maximum peer connections
max_peers = 50
# Bootstrap nodes
bootstrap = [
  # Bootstrap nodes TBD
]

[validator]
# Enable validator mode
enabled = true
# Validator key file
key_file = "/etc/computenet/validator.key"

[compute]
# Maximum concurrent jobs
max_concurrent = 4
# Supported runtimes
runtimes = ["wasm"]
# Resource limits
max_memory_mb = 8192
max_execution_time_ms = 60000

[logging]
level = "info"
format = "json"

Environment Variables

Configuration can also be set via environment variables:

  • COMPUTENET_NETWORK — Network to connect to
  • COMPUTENET_DATA_DIR — Data directory path
  • COMPUTENET_LOG_LEVEL — Logging verbosity
  • COMPUTENET_VALIDATOR_KEY — Validator key (for testing)

Configuration Sections

The configuration is organized into sections:

  • [node] — Basic node identity and paths
  • [network] — Networking and peer settings
  • [validator] — Validator-specific settings
  • [compute] — Execution environment settings
  • [logging] — Log output configuration
  • [metrics] — Prometheus metrics settings
NextOverview