The Rust daemon, dashboard and Buildroot integration are public under GPL-3.0 and build from the repository. A full flashable Antminer image is a different boundary: it reuses boot-critical vendor components that D-Central cannot redistribute in the source repository.
What is open and what is not redistributed
Open-source and non-redistributed DCENT_OS build inputs| Component | Repository status | Build/audit path |
|---|
dcentrald Rust mining daemon | GPL-3.0 source | Builds from a fresh clone for ARMv7 and AArch64 targets |
| React/TypeScript dashboard | GPL-3.0 source | Builds from the repository toolchain |
| Buildroot external tree and configuration | GPL-3.0 project source/configuration | Defines the minimal Linux userspace and integration |
| SoC kernel, FPGA bitstream, FSBL/U-Boot | Boot-critical vendor/upstream artifacts; not redistributed in the source repo | Must be supplied locally from firmware the operator is authorized to use and must match pinned hashes |
| Signed release package | Prebuilt guarded artifact | Contains SHA-256 manifests, Ed25519 public key and signed manifest |
Build the open daemon
git clone https://github.com/DCentralTech/DCENT_OS.git
cd DCENT_OS/DCENT_OS_Antminer/dcentrald
cargo build --release --target armv7-unknown-linux-musleabihf
# Amlogic targets use aarch64-unknown-linux-musl
These commands prove that the mining daemon source is buildable. They do not by themselves produce a complete bootable image.
Build a full image
The repository's production capsule currently admits the S9 target. It expects restricted boot inputs, release keys and a digest-pinned builder described in the release-candidate runbook. Direct development packaging fails closed when it cannot satisfy the release receipt.
make release RELEASE_TARGET=s9
Operators must extract the required boot components from firmware they are authorized to use. DCENT_OS does not make third-party redistribution rights appear by calling the surrounding stack open source.
Reproducibility status
Buildroot and pinned inputs improve repeatability, but this page does not claim byte-for-byte reproducible firmware. That claim requires a published environment, hashes from independent rebuilds and a documented comparison of any differences.
Audit trail
Boundary reviewed 2026-08-08. This page distinguishes buildable source from a complete redistributable boot image.
