Independent DCENT_OS Reviewer and Researcher Kit
Independent reviewers, miners and security researchers are invited to clone it, build it, flash only an exact guarded lane, break it and publish what fails. Positive coverage is not required. D-Central asks only for accurate hardware/build identification, safety and disclosure of supplied equipment.
Editorial independence
- D-Central does not require a positive conclusion, talking points, a preview copy, approval rights or removal of unfavorable results.
- Publish failed builds, failed flashes, rejected shares, instability, unsolicited network traffic and recovery problems.
- Disclose any miner, control board, travel, engineering time or other support supplied by D-Central.
- Embargoes apply only to responsibly disclosed security vulnerabilities and should be time-bounded by agreement.
- D-Central may request factual corrections, but the reviewer controls the conclusion and publication.
What D-Central can provide
| Input | Scope | Disclosure requirement |
|---|---|---|
| Compatible test hardware | A spare exact S9 Zynq/XIL or S19j Pro Zynq/XIL unit/control board may be available case by case; availability is not promised. | Name the supplied hardware and who paid shipping. |
| Artifact record | Exact filename, SHA-256 list, signed package manifest, release key fingerprint and model evidence page. | Publish the digest and lane tested. |
| Source/build orientation | Repository map, open-source boundary, vendor-input boundary and no-hardware test path. | State whether you built the daemon, dashboard or a complete image. |
| Recovery preparation | Model-specific evidence page, public recovery guidance and preflight checklist. | Do not flash until recovery is proven on the test unit. |
| Measurement template | Public field schema for power, hashrate, thermals, pool evidence and stability. | Publish raw measurements and failures. |
Minimum reproducibility checklist
- Clone the public repository and record the commit.
- Run the no-hardware tests and document every failure or excluded test.
- Build the daemon/dashboard and distinguish that from building a bootable image.
- Verify the vendor-boot-input boundary and all artifact signatures/checksums.
- Identify the exact miner, hash boards, control board, PSU and recovery route.
- Prove accepted pool shares; connected, enumerated or nonce flow is not enough.
- Measure wall power, pool-side hashrate, J/TH, temperatures, fans, rejects and stability with raw data.
- Capture network behavior and test authentication/update failure paths.
- Perform and document recovery before treating the installation route as reproduced.
Stable project description for coverage
DCENT_OS is D-Central Technologies' GPL-3.0 open-source Bitcoin mining firmware for Bitmain Antminer ASIC miners.
Current qualification: all 13 registry models are Released/Experimental. The verified prebuilt ledger currently contains exact S9 XIL and S19j Pro XIL files; that binary scope does not change the release status of other models, and no lane is promoted beyond its recorded install or recovery evidence. The GPL-3.0 daemon, dashboard and Buildroot integration are public, while complete Antminer images also require documented vendor boot inputs that are not redistributed in the source repository.
Start a review or research report
Read the benchmark protocol, security boundaries, source/build boundary and dated evidence ledger. Then contact D-Central with the exact hardware lane and intended test. Public project facts are also available at /wp-json/dc/v1/dcent-os.
Reviewer terms and evidence requirements reviewed 2026-08-29. No independent review is implied until a dated external report is linked from the evidence ledger.
Reproducibility: Build and run the software from source when reviewing behavior independently of packaged releases.
Companion tool — DCENT_Toolbox: Reproduce the read-only evidence pass with DCENT_Toolbox · Install DCENT_Toolbox.