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 →
1325 Rue Bergar, Laval, QC support@d-central.tech 1-855-753-9997 Mon-Fri: 8:30 - 18:00
Legacy S17 space-heater build: identity and service boundary ASIC miner reference image
Lifecycle not independently verified D-Central SHA-256

Legacy S17 space-heater build: identity and service boundary

Historical S17 enclosure project retained for service provenance; exact performance, acoustics, dimensions, electrical input, release and price are unverified.

Efficiency —

Full Specifications

Full technical specifications for this miner.
Model Legacy S17 space-heater build: identity and service boundary
Model Number Space Heater S17
Manufacturer D-Central
Algorithm SHA-256
Cooling Air
Interface Ethernet
Status Lifecycle not independently verified

Historical custom-build boundary

This route records a historical S17-based space-heater concept. No immutable build sheet, nameplate record or delivered-revision artifact was found that authenticates the former 50 TH/s, 2 kW, 55 dB, enclosure, chip-count, electrical, release-date or price claims as one shipped configuration. Those values are withheld.

What remains useful

A physical unit can still be serviced after its exact donor model, serial/nameplate, control board, hashboards, PSU, fan system and enclosure are recorded. OEM S17 specifications prove donor-machine lanes only; they do not prove a custom enclosure acoustic level, wall power or firmware tune.

The currently available S17/T17 conversion case is a separate DIY case product, not proof of this historical assembled profile.

Safety and firmware

Use the exact PSU nameplate for facility requirements and verify all protective grounding, airflow and over-temperature controls. Firmware must match the physical donor model and control board; a custom page name is not a firmware identity.