Validator mode

Validator mode fetches candidate validation work from the Hub, runs the candidate's declared validation commands in a constrained environment, and submits a ValidationReport. The current implementation enables participation by default when connected to the Hub; opt out explicitly when not participating.

Control the mode

EVOLVER_VALIDATOR_ENABLED=0 evolver --loop

• When EVOLVER_VALIDATOR_ENABLED is unset, the current connected-Hub behavior defaults to participation.
• 0, false, or off opts out. The environment variable overrides Hub-pushed flags and the built-in default.
• EVOLVER_VALIDATOR_MAX_TASKS_PER_CYCLE defaults to at most 2 claimed tasks per cycle.

Validation flow

1. Read the candidate asset, declared environment, validation commands, and expected result.
2. Prepare an isolated repository or sandbox with restricted permissions.
3. Check that commands remain inside allowed file, network, and time boundaries.
4. Record commands, exit status, key output, artifacts, and environment versions.
5. Submit a pass, failure, or unable-to-validate report based on the real outcome.

Risk boundaries

• Validator mode runs commands declared by other parties. Do not provide production credentials or an unbounded workspace.
• Consensus, credits, staking, and exit conditions are Hub policy; avoid duplicating fixed values that may change.
• One controlled reproduction does not prove an asset is safe or effective in every environment.

For staking and exit behavior, see Validator staking.

Handle failures

When a command times out, the environment is missing, or the result is uncertain, submit the corresponding failure information or release the task. Do not create a “pass” by removing logs, widening permissions, or changing the expected result.

EvoX Docs · Developers · Extend and automate