Skip to content
Small team, full backlog, zero orders dropped. Support replies are slower than we’d like. Read our status update → Zero orders dropped. Status → 📬 Check your spam folder — most of our replies land there. We do answer. Status update → 📬 Check your spam folder. Status →

ASIC Miner Firmwares

This page used to be a firmware mirror — dozens of hosted files, one download button per model, «firmware from all manufacturers at the click of a button.» It leads with the map now: a directory of every vendor’s official firmware channel, what each vendor actually publishes so you can verify a download, and where the real decision pages live. The archived files are still here, hashed and honestly labelled — but the vendor’s own channel is the first place to look, not the last.

What changed: the mirror stopped being the point

For years this page rehosted stock and custom firmware images so you could grab everything in one place. We no longer do that, and the reason is the same one our mining firmware security guide documents at length: a rehosted binary with no vendor-published hash to check against is unverifiable, and unverifiable is the wrong default for a file that gets total control of a revenue-producing machine. The documented mining-firmware attacks — the 2019 hAnt outbreak first among them — spread through exactly that pattern: plausible-looking firmware downloads outside the vendor’s own channel. A repair shop asking you to trust its rehosts instead of the vendor’s channel would be teaching the wrong habit — which is why our own archive is labelled as a mirror, published with hashes, and points you at the vendor first.

So, plainly: this page is a directory of official channels, not a download menu. D-Central does still host an archive of older firmware images, recovery images and manufacturer service documents, and we publish a SHA-256 for every file in it — but it is a mirror, not an official channel, we do not add to it, and it is excluded from search indexes. Where a file’s upstream source is established we name it; where it is not, we publish Source: Unknown rather than guess a vendor URL. The full record is at the firmware mirror provenance page, and if you are reverting a machine rather than hunting a file, start at restore stock firmware. The firmware we develop and distribute ourselves — the open-source (GPL-3.0) DCENT_OS and DCENT_axe stack — ships from our /flash/ browser flasher, each factory image with a published SHA-256. We hold our own downloads to the same standard this page applies to everyone else’s.

Official firmware channels by vendor

The single highest-value habit in mining firmware security costs nothing: bookmark the vendor’s official channel once, verified carefully, and only ever download from the bookmark — never from a search result, a marketplace listing, a forum attachment or a link someone sent you. Channels and verification material below were last re-verified against the live vendor pages on 2026-08-13.

Vendor Official channel How you verify a download
Bitmain (stock Antminer) service.bitmain.com/support/download — reached from bitmain.com via Customer Support → Firmware Download → your model Published file hashes: none that we can confirm. On signed-firmware Antminers the machine itself refuses images Bitmain didn’t sign — that on-device signature check is the practical integrity mechanism.
Braiins (Braiins OS / OS+) braiins.com/os-firmware/download; release archive at downloads.braiins.com The strongest verification story of any industrial vendor: a SHA-256 published beside every release asset, plus a GPG public key with verify-by-GPG instructions.
VNish Four official domains, per the vendor’s own advisory: vnish.group, vnish.us, vnish.cn, vnish.es No published checksums. The vendor’s stated authenticity tells are behavioral: genuine builds charge at most a 2.8% dev fee, and monitoring only works with firmware from the official sites.
Luxor (LuxOS) luxor.tech/firmware — delivery is tool-mediated through LuxOS Commander / LuxOS Installer rather than loose binaries No public checksums; authenticity rests on obtaining the tool itself from luxor.tech.
ePIC Blockchain (UMC OS) epicblockchain.io/support/firmware — download buttons route to the github.com/epicblockchain release pages No vendor hash list, but GitHub attaches a platform-computed SHA-256 digest to every release asset.
Bitaxe (ESP-Miner / AxeOS) github.com/bitaxeorg/ESP-Miner Releases — the sole release channel; the web flasher and AxeOS OTA both pull from it GitHub’s per-asset SHA-256 digest, plus fully auditable open source.
D-Central (DCENT_OS / DCENT_axe) The /flash/ browser flasher and the public GPL-3.0 repositories Published SHA-256 per factory image; open source; experimental images labeled as exactly that.

How to actually run a hash check — and what to do when a vendor publishes nothing to check against — is covered step by step in the firmware verification guide and in the before-you-flash path of the security guide.

Stock firmware for Whatsminer, Avalon and Innosilicon hardware

Same rule, different vendors: get stock images from the manufacturer’s own support portal, not from rehosts — ours or anyone else’s. For MicroBT hardware, start with the Whatsminer firmware guide, which walks that ecosystem’s actual options; the Whatsminer M-series decoder tells you which generation you own first. Canaan Avalon units are their own world — Kendryte RISC-V controllers with tuning tables encrypted on-device — and the Avalon A-series decoder is the honest entry point. For Innosilicon units, firmware ships with the machine or comes from Innosilicon support; our Innosilicon repair pages cover the hardware side.

Choosing custom firmware — and what it actually costs

Dev fees, stated as the ranges they actually are: Braiins OS+ runs a 2–2.5% range (effectively waived when mining on Braiins Pool), VNish runs 2–2.8% depending on model, LuxOS charges 2.8%, and DCENT_OS is 0%. On MicroBT hardware, note the distinction the marketing tends to blur: the ePIC UMC is a replacement controller board (hardware); ePIC’s UMC OS firmware carries a 1.5% dev fee (since 2026-01-26). The full feature-by-feature decision lives on the firmware comparison page. Before committing to anything on an S19/S21-generation machine, check the ASIC firmware lock tracker — units with post-March-2024 Amlogic control boards need a documented unlock before any third-party install — and the model pages for the machines we get asked about most: the Antminer S19 XP firmware hub, the Antminer T21 firmware hub, and the S19 and S21 family hubs.

Recovery images and SD-card reflashes

The most legitimate reason people came to this page was recovery: a bricked control board, a bad flash, a machine that needs a known-good image. That need is better served by procedure than by a file dump. The SD-card firmware recovery guide covers the reflash procedure generation by generation, and the control-board recovery index maps every board family — Zynq, BeagleBone, Amlogic, CVitek, ESP32, Kendryte — to its boot source, recovery entry and reflash method. And when a board will not come back no matter what you feed it, that is what the repair bench is for.

Firmware questions we actually get

Where do I download official Antminer firmware?

From Bitmain’s own portal at service.bitmain.com/support/download, reached from bitmain.com — Bitmain’s published fraud statement names bitmain.com as its only official website. Firmware for the same models offered anywhere else is a rehost at best, and with no Bitmain-published reference hash, a rehosted copy cannot be verified after the fact.

Should I run stock or custom firmware?

Any sale or repair we perform ships with a factory reset and the latest stock firmware — stock is a perfectly good default, and operators who don’t want to think about tuning are often best served staying on it. Custom firmware earns its dev fee when you have a specific goal: efficiency tuning, per-machine power targets, heat-reuse setups, or Stratum V2. The comparison page is the decision tool.

Is VNish available for the Antminer S19 series?

Yes — VNish covers the S19 family broadly. Download it only from the four domains VNish itself names as official (vnish.group, vnish.us, vnish.cn, vnish.es); the dev fee is in the 2–2.8% range depending on model.

Do you still host firmware files?

Yes — an archive of older images, recovery images and manufacturer service documents, kept because a repair bench needs known-good files on hand. We publish a SHA-256 for every one of them, and we say Source: Unknown wherever we cannot establish where a file came from. Be clear about what that hash proves: the file has not changed since we mirrored it. It does not prove the manufacturer built it. A rehost — even an honest one — is a weaker link in the verification chain than the vendor’s own channel, which is why the directory above comes first and the archive is documented rather than promoted.

Is there custom firmware for Whatsminer or Avalon?

For MicroBT hardware the practical aftermarket path today is ePIC’s ecosystem: the UMC replacement controller board, running ePIC’s UMC OS firmware at a 1.5% dev fee — details and trade-offs in the Whatsminer firmware guide. Avalon controllers keep their frequency/voltage tables encrypted on-device, which is a big part of why a general Avalon aftermarket scene has not materialized; the Avalon A-series decoder explains the architecture honestly rather than promising firmware that does not exist.