Node startup continues even when required environment variables are missing

[imprint-rowboat]

Overview

When starting base/node, the process may continue running even if required environment variables are missing or incorrectly configured. This can lead to runtime failures later in the lifecycle that are harder to diagnose.

Problem Description

If a required environment variable is absent or malformed:

• The node may still start without an immediate error.
• Failures occur later during network initialization or runtime operations.
• Operators must inspect logs or configuration manually to identify the root cause.

Failing fast would improve reliability and operator experience.

Expected Behavior

When required environment variables are missing or incorrectly configured, the node should fail fast during startup instead of continuing to run. The startup error should clearly indicate which configuration values are missing or invalid, allowing operators to correct the issue immediately.

Steps to Reproduce

1. Remove or misconfigure a required environment variable.
2. Start base/node.
3. Observe that the process starts but fails later or behaves unexpectedly.

Proposed Solution

Add startup-time validation for all required environment variables so misconfigurations are detected immediately. When a required variable is missing or invalid, the node should exit early with a clear, descriptive error message before any network or service initialization begins.