Current answer
The Antminer S19 has driver-path bring-up evidence but no public artifact or supported install route. It does not inherit S19 Pro or S19j Pro evidence.
Antminer S19 evidence and readiness
| ASIC | BM1398 |
|---|
| Control-board lane | Zynq / Xilinx |
|---|
| Artifact | No public artifact |
|---|
| Mining evidence | Bring-up — shares the S19 Pro driver path; no S19 accepted-share claim |
|---|
| Install readiness | In development; no public install route |
|---|
| Production status | Not supported for public installation |
|---|
Dated evidence ledger
| Website review | 2026-08-08 |
|---|
| Published proof scope | The public platform matrix records driver-path bring-up only for the exact S19 row. |
|---|
| Open evidence gap | Accepted-share proof, signed package, first-install runbook, soak and recovery capstone. |
|---|
| Build / commit | No model-specific commit receipt is asserted on this page; use the named artifact manifest or the current repository commit when reproducing a test. |
|---|
| Independent reproduction | No independent reproduction is claimed unless a dated proof link is added here. |
|---|
What the status does — and does not — prove
Mining evidence answers whether DCENT_OS has produced accepted pool shares on named hardware. Install readiness answers whether a general operator can safely move from the original firmware to this build and recover. Those are independent questions.
- Mining verified means accepted shares, not merely detected chips or nonce flow.
- Guarded artifact means a signed file is downloadable but an install, boot, soak, or recovery proof is still incomplete or unpublished.
- Lab-only means the source or runtime path has evidence without a general public installation route.
- In development means there is no public artifact for operators to flash.
Known limitations
- S19 does not inherit S19 Pro evidence simply because both use BM1398-era paths.
- S19j Pro uses a different ASIC and its artifact must not be used on an S19.
- No S19 download, checksum, release note or supported recovery route is published.
Do not infer support from the miner name alone. Identify the exact control board, keep a known-good SD/UART recovery path, and never test experimental firmware on revenue-critical hardware.
Identify the exact control board
Use the ASIC control-board reference and physical board markings before interpreting this page. Connector shape, miner family and an ASIC generation are not sufficient identifiers. No stock photo or simulated dashboard is presented as proof for this lane.
Artifact-to-evidence receipt
| Exact public artifact | None published |
|---|
| Source commit / Git tag | Not recorded in the public website receipt for this artifact; do not infer one from the current repository head. |
|---|
| Manifest / signature | No public package or manifest. |
|---|
| Raw pool / console proof | No model-specific raw proof bundle is linked from this website page yet. |
|---|
| Independent reproduction | None published and linked. |
|---|
| Change history | Use the dated evidence ledger; no separate model changelog is claimed. |
|---|
Test this exact lane and publish success or failure. A report must identify the model, board, artifact digest, source/build state, raw logs and recovery outcome.
Performance data
No independent stock-versus-DCENT_OS benchmark dataset is asserted here. D-Central will publish hashrate, wall power, J/TH, thermals, fan RPM, reject rate and stability data only with the raw measurements, hardware identifiers, build commit, pool-side proof and test duration attached. See the benchmark and reproduction protocol.
Reviewed against the public repository and live artifact directory on 2026-08-08. Corrections: contact D-Central or open a repository issue.
