VNISH GLOBAL · Academy
Listed, Route-Verified, Installed and Site-Validated Are Different States
A catalog entry is discovery, not installation proof. Route-verified means a specific model, variant, control board, build and install path were checked together. Installed describes one device state; site-validated adds measured operation under stated site conditions. Skipping a state turns uncertainty into an unsafe claim.
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
- Listed: the item exists in a current VNISH data source. It does not prove that a particular device matches it.
- Route-verified: the exact route passport has model, cooling class, board, current state, install method, filename, version, size, SHA-256 and a recovery path.
- Installed: readback from the target device confirms the expected build identity. This alone does not prove stable mining.
- Site-validated: the operator records cooling, wall power, pool-side work, errors and an observation window for that unit and site.
1.3.5 evidence
Current verified artifact example
Example only for Antminer S21 air-cooled / AML / NAND. It is not a route for Hydro, Immersion, XIL, CV or BB hardware.
- Filename
- vnish-s21-aml-nand-v1.3.5.tar.gz
- Bytes
- 21,541,929
- SHA-256
- da3d6312be551aeb8af90812dd41567cbaa3b87eb957dc7273414b9efbc1b6d9
Release 1.3.5manifest.jsonSHA256SUMS.txtChoose an exact build
Limits and stop conditions
- SHA-256 proves byte equality with a published value; it does not by itself prove origin, compatibility, safety or recoverability.
- If a required route-passport field is UNKNOWN, stop and resolve it rather than choosing by family name.
- One validated unit is evidence for that unit and cohort, not every device in a fleet.
Reusable artifact
| # | Field | Checked | Evidence / note |
|---|---|---|---|
| 1 | Exact model, submodel and cooling class | □ | |
| 2 | Control-board platform and identifier | □ | |
| 3 | Current firmware/security state | □ | |
| 4 | Target filename, version, size, SHA-256 and source | □ | |
| 5 | Install route, recovery route, checked_at and reviewer | □ |
Copy this structure into a change record; never place passwords, keys or private access details in it.
Primary sources
- VNISH GLOBAL firmware catalog Reviewed 2026-09-10
- VNISH 1.3.5 release record Reviewed 2026-09-10
- VNISH 1.3.5 manifest Reviewed 2026-09-10
- VNISH 1.3.5 SHA256SUMS Reviewed 2026-09-10