No direct control
No reboot, factory reset, firmware flashing, overclocking, tuning, or voltage changes.
Read-only boundary
Safety & Scope
Bitcoin Mining Troubleshooter provides diagnostic decision support over evidence supplied to the AI session. It is not a miner-control backend.
In scope
Evidence you can bring.
Use logs, scanner exports, screenshots, repair history, network output, power and thermal evidence, and incident descriptions that you already have.
- Miner logs
- BTC Tools-style scanner exports
- Fleet CSV / JSON / XLSX evidence
- Screenshots and incident notes
- Repair history
- Pool symptoms and connection evidence
- User-supplied network, power, and thermal evidence
Out of scope
No state-changing equipment actions.
If a possible remediation changes operational state, the troubleshooting response should recommend the read-only observation that would justify or reject that remediation instead of executing it.
No configuration writes
No pool or wallet changes, static-IP changes, or network reconfiguration.
No switching
No PDU or breaker switching, curtailment actions, or arbitrary shell commands that change operational state.
Evidence rules
Unknown stays unknown.
Preserve source meaning
Missing, blank, and unparseable measurements remain Unknown; explicit source units are preserved; derived rates disclose denominators and material exclusions.
Do not overclaim telemetry
Scanner success means a response returned. It does not prove healthy hashing, pool authorization, accepted shares, or electrical health.
Prefer shared causes first
Correlation is not automatically causation. Shared rack, subnet, firmware, power, cooling, and timing hypotheses should be considered before mass independent hardware diagnoses.
Operational use
Decision support, not procedure replacement.
Use the output alongside site procedures, electrical safety requirements, manufacturer guidance, and qualified personnel. Preserve original evidence before destructive troubleshooting.
Questions about scope, safety, or private evaluation can be sent to austin@wnclogiclab.com.
View technical safety document →