VNISH Ninja · Academy
Before Changing ASIC Firmware: Evidence and Recovery Checklist
Before changing firmware, freeze a small evidence pack that identifies the device, the planned bytes and the recovery owner. The pack does not choose a file for you; it makes a wrong assumption visible before the miner is changed.
From exact hardware to accepted work
- Identify exact hardware
- Resolve this site route
- Verify file evidence
- Prepare recovery
- Install one canary
- Read back accepted work
Working method
- Identify the exact model, submodel, cooling type and control-board platform using read-only evidence. Family names such as S21 are not enough.
- Capture the current firmware version, security or lock state, relevant configuration, screenshots and recent logs. Store secrets outside the pack.
- Resolve the target only through the current VNISH route for the exact combination. Record filename, version, byte size, SHA-256, source URL and retrieval time.
- Write the recovery path before change: required image or method, who owns the decision, access dependencies and the condition that triggers recovery.
- Define stop conditions. Any mismatch, UNKNOWN mandatory field, unexpected reboot loop, missing boards or unsafe cooling state means stop and escalate.
Limits and stop conditions
- Aftermarket firmware is not made or approved by BITMAIN. BITMAIN warns that unauthorized firmware or overclocking can cause malfunction and affect warranty; current vendor terms and the sales contract control.
- Do not open a miner merely to identify a board when a read-only method is available.
- Do not assume rollback is universal or that returning to stock restores warranty or removes traces.
Reusable artifact
| # | Field | Checked | Evidence / note |
|---|---|---|---|
| 1 | Device identity and board evidence | □ | |
| 2 | Before-state screenshots, config export and logs | □ | |
| 3 | Target file identity and SHA-256 | □ | |
| 4 | Recovery owner, method and dependencies | □ | |
| 5 | Change window and explicit STOP triggers | □ |
Copy this structure into a change record; never place passwords, keys or private access details in it.
Primary sources
- BITMAIN — generic online-upgrade precautions (updated 2026-03-03) Reviewed 2026-09-10
- BITMAIN — read-only control-board information Reviewed 2026-09-10
- BITMAIN — Product Warranty Reviewed 2026-09-10
- BITMAIN — Malware and remote attacks Reviewed 2026-09-10