Watt ServiceNet is configured entirely through environment variables. Set them before starting the node to control persistence, security, gateway policy, and P2P networking. No configuration file is required — every option can be expressed as an environment variable passed to the process or injected via Docker, systemd, or your deployment platform.
Core
Storage
When neither SERVICENET_DATABASE_URL nor SERVICENET_REGISTRY_FILE is set, the node uses in-memory storage and all state is lost on restart. See Storage Backends for a full comparison.
Security
Generating a Secret Broker Key
Generate a cryptographically random key before your first PostgreSQL-backed deployment:
Pass the output as SERVICENET_SECRET_BROKER_KEY:
Never use the placeholder key (BwcHBwcH...) shown in example configs in a production deployment. Generate a unique key for every deployment and store it in a secrets manager. Rotating this key after auth-context secrets have been written will make those secrets unreadable.
Gateway Policy
P2P Networking
The variables below control the Iroh-backed P2P sync layer. P2P is disabled by default.
For step-by-step P2P configuration, see P2P Setup. For federation trust policy, see Federation.