Configuration and Management

Iroha configuration has two authoritative layers:

• local peer and client configuration, stored in TOML files and read at process startup
• on-chain configuration, changed by transactions through SetParameter

Use local configuration for node identity, addresses, logging, storage, and client signing keys. Use on-chain configuration for values that must be agreed by the network and replayed deterministically.

Production behavior must come from these configuration layers. Environment variables may be convenient for supplying test inputs to local tooling, but they are not production feature gates and do not replace committed configuration.

The main configuration entry points are:

• Genesis
• Client configuration
• Keys for network deployment
• Running on bare metal
• Peer configuration reference