Contribute to DCENT_OS & the D-Central Open-Source Stack
Quick answer
How do I contribute to DCENT_OS?
We build on open protocols and open predecessors, so our own firmware and tools are open too. If you want to shape where DCENT_OS goes, the door is open — and being early is an advantage, not a barrier.
The repos
Everything lives under github.com/DCentralTech, GPL-3.0:
- DCENT_OS — open mining firmware for ESP32-S3 (Bitaxe-class) miners.
- DCENT_Toolbox — the companion flashing / monitoring / control tooling.
- DCENT_axe · Voice · Torrent — the wider sovereign-stack projects.
How to send a change
- Read the repo’s
CONTRIBUTING.mdandCODE_OF_CONDUCT.md— andGOVERNANCE.md/SECURITY.mdif your change touches process or security. - Fork the repo and clone your fork, then branch off
main:
git clone https://github.com/<you>/DCENT_OS cd DCENT_OS git checkout -b my-fix
- Build and test it yourself — the README has a tiered “test it yourself” path and platform docs. If you can flash it in the browser at /flash/, you can validate a firmware change end-to-end.
- Commit, push your branch, and open a pull request against
maindescribing what and why. - Found a bug you can’t fix? Open an issue on the repo — a clear, reproducible report is a real contribution.
Licensing & credit
DCENT_OS is GPL-3.0: contributions are licensed under the same
terms as the project (inbound = outbound), and upstream projects we build on are credited in each repo’s
THIRD_PARTY_NOTICES.md. Security issues: use the repo’s SECURITY.md process
rather than a public issue. Not a coder? The most useful non-code contribution is a precise bug report or a
field report from real hardware.
Related: Build With D-Central (API + data + OSS index) · DCENT_OS · web flasher · the sovereign stack.
Related products, repair, and setup paths
- immersion cooling hub
- home immersion cooling guide
- ASIC miners for immersion planning
- ASIC cooling parts
- airflow shroud before immersion
- compare miner specs in the database
- ASIC repair support
Last reviewed July 21, 2026.
