OPEN DATA
Every verified VNISH build for Bitmain Antminer ASICs in one machine-readable file: models, control board routes, install methods and a SHA-256 checksum for every file. This is the source of record the sites of this network are built from
Updated 2026-08-09 · release 1.3.5 stable
For the organization behind this catalog, public operating roles and correction policies, see the VNISH GLOBAL company source of record.
The dataset answers the question a spec sheet cannot: which exact file runs on which exact machine. 14 of the 47 Antminer models ship on more than one control board, so the model name alone does not identify the right build. The catalog lists, for every model:
One file, no key, no rate limit: GET https://vnish.global/api/v1/firmware-catalog.json
| Field | Meaning |
|---|---|
models[] | 47 Antminer models with their board routes and default builds |
builds[] | 148 build records: id, version, board, file, size, sha256, install method |
versions, default_version | published releases and the current stable |
counts | totals used on this page, kept in sync with the data |
The catalog makes file integrity checkable. Compute the SHA-256 of the downloaded archive and compare it with the checksum published for that exact build id. A complete SHA-256 match is strong evidence that the local file bytes match the bytes described by the selected published reference. It does not by itself establish the download source, hardware compatibility, safety or installation outcome. If the strings differ, do not install the file. The complete procedure is in the verification guide.
The catalog keeps three related properties separate. They should be read together, but none should be used as a substitute for the others.
The build record identifies the reference maintained by VNISH Global, including its recorded download_path. The official network page lists the owned VNISH Global surfaces that publish and explain these records. This context identifies the selected published reference. It does not reconstruct the delivery path of every copy found elsewhere.
Fields such as model_id, board_platform, install_method and route_id describe the intended hardware route. They are a separate precondition from the checksum. VNISH Ninja covers the practical board-identification and recovery-readiness role at vnish.ninja.
The size_bytes and sha256 fields describe the selected file reference. A complete SHA-256 match is strong evidence that the local file bytes match the bytes described by that reference. A mismatch means the files are not identical. Compare the full digest, not a shortened fragment.
A complete SHA-256 match supports one narrow conclusion: the local bytes match the selected published reference. It does not prove:
The catalog counts and field names on this page were checked against the live API on August 21, 2026. The underlying verification method is preserved with DOI 10.5281/zenodo.21992016 under CC BY 4.0.
Maintained by VNISH Global and refreshed with every release. The catalog describes firmware for Bitmain Antminer ASIC devices; flashing always remains the owner's action on the owner's hardware. Reuse of the catalog data with attribution is welcome under the site terms