DCENT_OS Evidence and Readiness Status
DCENT_OS 0.9.0: exact-board Experimental status
beta20261002 has 29 exact-board status cards; 29 sets have retained or verified public static URLs. There are 17 raw SD images, 11 route-restricted archives and one BeagleBone developer payload. Only 13 raw-image rows have a lab SD route; 4 are inspection only while permissions conflict. Physical qualification is pending. The automated installer route is unavailable because its signed host does not resolve. Static file availability and installation permission are separate.
Choose your exact model and board · Files, verification and installation boundaries · Report an issue · Historical July record
Historical July-registry evidence; identity ledger dated 2026-09-01. These older status and hardware rows do not describe current October download availability. The current beta20261002 catalog lists 29 exact-board static file sets. Newly hosted artifacts do not establish physical boot, accepted shares, endurance or recovery qualification; use each current card for its installation restrictions.
Historical identity and status ledger — 1 September 2026
Historical July-registry evidence; identity ledger dated 2026-09-01. These older status and hardware rows do not describe current October download availability. The current beta20261002 catalog lists 29 exact-board static file sets. Newly hosted artifacts do not establish physical boot, accepted shares, endurance or recovery qualification; use each current card for its installation restrictions.
Historical hardware evidence table — July registry
Current October release
DCENT_OS 0.9.0 beta20261002 publishes static files for 29 exact-board Experimental status cards: 17 raw SD images, 11 restricted archives and one BeagleBone developer payload. Thirteen raw-image rows have lab-only SD routes; four permit inspection only. Three Amlogic rows have host-driven lab workflows and six deny installation/update. The signed automated installer host is unavailable; static downloads and installation permission are separate. Publication and signature verification do not prove physical boot, accepted shares, recovery or production qualification.
Use the current exact-board release cards and signed companions and installation and recovery decision guide. Development-key approval does not establish third-party kernel, boot or FPGA source correspondence or redistribution permission. The six retained historical scoped source bundles and their limits are listed in the release record. Additional Amlogic packages have partial source coverage; their full legal inventory and complete vendor/dependency correspondence are not established.
The evidence-state definitions below remain useful. The later model rows and machine-readable legacy API describe the historical July registry, not the full October download inventory.
How to read the evidence states
| State | What it proves | What it does not prove |
|---|---|---|
| Artifact available | A named signed file and checksum are published for an exact miner/control-board lane. | It does not prove a generally validated first-install or recovery path. |
| Mining verified | Accepted pool shares are documented on named bench hardware. | It does not prove installation readiness or current-binary reproduction. |
| Guarded artifact | A file exists, but a required install, boot, soak or recovery proof remains incomplete or unpublished. | It is not production support. |
| Lab-only / bring-up | Source, enumeration, nonce, hashing or an earlier runtime path has evidence. | It does not create a public image or supported route. |
Historical July artifacts: evidence first, file second
Antminer S9 Zynq/XIL
A signed sysupgrade package and SD image exist, and accepted-share mining is documented. The public repository still lacks a witnessed current-artifact first-install, boot, soak and recovery capstone. Review the exact S9 evidence page and release record. S9i, S9j and other control-board labels do not inherit this artifact.
Antminer S19j Pro Zynq/XIL
A signed Zynq/XIL package exists and accepted-share mining is documented. A guarded DCENT_OS-to-DCENT_OS update path has evidence; the first installation from vendor stock firmware remains open. BeagleBone and Amlogic are separate lanes. Review the exact S19j Pro evidence page and release record.
Historical July rows: no public artifact in that registry
These historical July rows do not describe current October file availability. The current record separately lists all 29 exact-board static file sets, including nine Amlogic packages and the BeagleBone developer payload. Read the exact card: inspection downloads, authorized lab workflows, existing-runtime updates and first-install-only archives have different permissions. No current-artifact physical boot, accepted-share, endurance or recovery qualification is claimed.
- Antminer S19: driver-path bring-up only; no accepted-share claim, public artifact or install route.
- Antminer S19 Pro: cold boot, chain enumeration and nonce flow; no current accepted-share proof or public artifact.
- Base Antminer S21/BM1368: earlier accepted-share runtime evidence; not rerun on latest binaries, no artifact, and stock AMLCtrl installation remains blocked.
- S17/T17 and every unnamed model/control-board combination: no public artifact is implied by source folders, shared chips or family names.
Historical July release and build boundaries
The GPL-3.0 Rust daemon, dashboard and Buildroot integration are public. A complete Antminer image also requires documented boot-critical vendor inputs that are not redistributed in the source repository. Read the source/build boundary, verify published checksums, and distinguish source buildability from complete-image provenance.
Before any persistent write
- Match the exact miner and control-board lane.
- Read the model evidence page and named release record.
- Prove a known-good SD/UART recovery route on the actual test unit.
- Back up the current state and record hardware revisions.
- Do not test guarded firmware on revenue-critical hardware.
- Report failures, short sanitized diagnostics and the exact artifact digest through the existing contact route; remove credentials and personal identifiers.
Historical registry API and current release catalog
The October publication catalog lists 29 current exact-board status cards and static file contracts separately from the legacy July API.
The canonical project record is available at /wp-json/dc/v1/dcent-os. It retains the historical July registry and separates artifact, mining, install and production fields. Use the current October catalog for static availability; do not merge the two evidence periods.
Historical July evidence heartbeat
Website review: 8 August 2026. Artifact set: beta20260709. No independent benchmark reproduction or independent security audit is claimed. Corrections can be submitted through the repository or D-Central contact page.
Companion tool — DCENT_Toolbox: When your gear is an S9, install with DCENT_Toolbox.
