Monitoring and maintenance
Prioritize active obligations and their deadlines. An idle scanner does not establish that payments, proofs, or nonces are progressing.
Operational signals
Section titled “Operational signals”| Watch | Investigate |
|---|---|
| Swap phase age and deadlines | Stalled award, payment, proof, or settlement |
| Ethereum providers and nonces | Stale reads, clock skew, private inclusion failures |
| Monero wallet and daemons | Sync, payment visibility, frozen inputs, mature inventory |
| Proof requests and funds | Ambiguous requests, attempt limits, requester balance |
| Admission state | Recovery-only conditions and unacknowledged losses |
| Storage | Free space, state errors, artifacts, and log growth |
These signals come from logs and state; no separate metrics endpoint is provided.
Logging
Section titled “Logging”The example writes debug JSON to synchronous stderr and a private append-only file. Remote errors can expose sensitive material; diagnostic bodies may reach 32 MiB. Treat logs as private evidence.
redact_urls = true removes HTTP(S) locators, but cannot remove other secret text; the example is false. Log files must be regular and owner-only. Rotate externally and restart to reopen the file.
State and artifacts
Section titled “State and artifacts”The state file has a 16 MiB envelope. Its sibling .artifacts/ directory is reserved for managed witnesses, proofs, and recovery files; keep configuration, secrets, ELF, and logs elsewhere.
The example 1,024 MiB artifact threshold stops new bids while recovery continues. Terminal cleanup deletes owned files and syncs directories. Unknown files are preserved.
Maintenance
Section titled “Maintenance”Stop the runner before manual inspection or configuration changes. Protect backups and keep one active owner. Follow upgrade requirements when changing releases. Preserve evidence and investigate losses before using recovery commands.