DCENT_axe – D-Central Technologies
DCENT_axe: Rust BitAxe Firmware with AI Control
Experimental BitAxe firmware written in Rust, with MCP-based AI control, AxeOS-compatible API targets, autotuning work, and Stratum V2 development in progress. Closed beta today; public beta rollout planned for summer 2026. Flash only hardware you can recover.
Current Status: Public Beta Preparation
DCENT_axe is still experimental. Public beta images, onboarding notes, supported hardware updates, checksums, and recovery instructions will be published progressively. Until a matching image is listed for your exact model and board revision, support is incoming.
Beta Risk
Beta firmware can brick hardware, break WiFi setup, misread sensors, corrupt configuration, or require USB/UART recovery. Only flash miners you are prepared to recover, repair, or lose downtime on.
FAFO Boundary
If you do not want to debug firmware, serial logs, recovery images, and unstable behavior, wait for a later release. Public beta means test hardware only.
Open Source Target
D-Central intends to publish DCENT_axe under GPL-3.0 after the beta period. Public repository access is planned, but the current beta rollout remains staged.
Three Modes: Heat, Mine, Hack
DCENT firmware is being organized around three operator profiles so beginners can stay protected, daily miners can tune efficiently, and advanced users can inspect and automate the machine.
Basic / Heat
Simple thermal targets, conservative settings, and home-heating behavior for users who want a quiet Bitcoin heat source without touching low-level controls.
Standard / Mine
Daily mining controls for pool setup, uptime, efficiency, temperature management, and measured tuning once the hardware is stable.
Advanced / Hack
Developer-facing controls for logs, MCP tools, automation, experimental tuning, and beta diagnostics. This mode is for people who accept the full FAFO boundary.
What is DCENT_axe?
DCENT_axe is a clean-room implementation inspired by the AxeOS project that proved open-source BitAxe firmware is viable. It is a ground-up rewrite of BitAxe firmware in Rust, using ESP-Miner as a protocol reference. Rust is designed to prevent many memory-safety bug classes in safe code, but beta firmware can still have logic bugs, driver issues, sensor mismatches, and hardware-specific failures.
The defining design target is the built-in MCP (Model Context Protocol) server. DCENT_axe is being built so compatible AI assistants and automation systems can inspect miner status, adjust frequency and voltage, manage pools, run tuning workflows, and expose hardware state through structured tools instead of brittle scraping.
The beta track targets the major BitAxe ASIC families: BM1370 (Gamma, GT), BM1366 (Ultra, Hex Ultra), BM1368 (Supra, Hex Supra), and BM1397 (Max). Compatibility will be published image by image. Always match the firmware file to the miner model, chip family, board revision, sensors, and power monitor before flashing.
Built on ESP-IDF v5.3+ with Rust for ESP32-S3 BitAxe-class hardware. Do not flash until the public beta lists a matching image and recovery path for your exact device.
Why DCENT_axe?
DCENT_axe is being built for transparent, local-first miner control. The public beta will document what is available in each build, what remains experimental, and which devices are safe to test.
AI-Native Control (MCP)
The MCP interface is planned to expose 12+ tools for compatible AI clients and automation systems. Target functions include status monitoring, frequency and voltage changes, pool management, tuning workflows, and fan control through a structured local API.
Memory-Safe Rust
Rust’s ownership model helps eliminate many memory-safety failures in safe Rust before code reaches your ASIC. That is a strong foundation, not a guarantee. Embedded firmware still needs careful validation across sensors, power stages, networking, mining protocol behavior, and recovery flows.
Stratum V2 Track
Stratum V2 support, including encrypted transport and job-declaration work, is part of the DCENT_axe development track. Public beta release notes will separate what is enabled, what is behind feature flags, and what is still under test.
Smart Autotuner
Four tuning modes for every scenario: Max Hashrate pushes your chip to its limit. Best Efficiency finds the sweet spot of J/TH. Target Watts holds a power budget you set. Target Temperature keeps thermals where you want them. The autotuner calculates values at runtime based on your specific silicon — not presets from a spreadsheet.
Tamagotchi Mining Companion
Your BitAxe OLED display comes alive with a pixel-art creature that evolves alongside your mining journey. Six evolution stages — Egg, Hatchling, Miner, Veteran, Legend, Titan — driven by real mining milestones. 16 tracked achievements unlock as you mine. The 128×32 SSD1306 display cycles through an 8-page carousel showing hashrate, temperature, shares, and your companion’s mood. Mining should be fun.
Solo Miner’s Luck Calculator
Every solo miner asks the same question: “Am I lucky or unlucky?” DCENT_axe answers it with math. The built-in luck calculator shows your probability of finding a block at current network difficulty, expected time-to-block at your hashrate, and cumulative luck since you started. No more guessing. No more anxiety. Just cold, honest statistics — updated in real time.
Multi-Pool Failover
Pool failover is being designed around transparent local control. Future updates may add hashrate splitting for multi-pool strategies or an optional, visible contribution stream for users who want to support development. There is no hidden mandatory fee target.
Home Assistant Integration
MQTT and Home Assistant integration are planned so BitAxe miners can expose hashrate, temperature, power, and mining state to local automations. This is especially useful for Bitcoin space heater setups where heat output and room conditions matter.
DCENT_axe Target Hardware
The public beta is expected to target these BitAxe families first. Every public image will be tied to a specific model and hardware revision. If your exact device is not listed with a matching file, do not flash it yet.
| ASIC Chip | BitAxe Models | Typical Hashrate Class | Beta Image Status | Flash Guidance |
|---|---|---|---|---|
| BM1370 | Bitaxe Gamma, Bitaxe GT | ~1.0-1.2 TH/s class | Support incoming | Check model, board revision, sensors, and release notes before flashing. |
| BM1366 | Bitaxe Ultra, Bitaxe Hex Ultra | ~500 GH/s-3 TH/s class | Support incoming | Wait for a matching image and published checksum. |
| BM1368 | Bitaxe Supra, Bitaxe Hex Supra | ~600 GH/s-3.6 TH/s class | Support incoming | Confirm exact build compatibility before flashing. |
| BM1397 | Bitaxe Max | ~400 GH/s class | Support incoming | Do not flash unsupported binaries across chip families. |
Public beta downloads: support incoming | Current guidance: check back before flashing | Recovery path required
MCP: AI-Assisted Miner Control
The planned Model Context Protocol interface exposes miner state and control operations to compatible local agents. Public beta builds will document the available tools, permission model, and safety limits.
Monitor
- get_status — Live hashrate, temperature, power draw, uptime, shares accepted/rejected
- get_asic_info — Chip model, frequency, voltage, silicon grade (A/S/B/C tier)
- get_network — WiFi signal strength, IP address, connection quality
- get_history — Rolling performance data that survives reboots
Control
- set_frequency — Adjust ASIC clock speed in real time
- set_core_voltage — Tune voltage for efficiency or performance
- set_fan_speed — PWM fan control from whisper-quiet to full blast
- set_pool — Switch pools without touching a config page
- toggle_mining — Soft pause/resume without rebooting
- set_schedule — Time-based mining profiles
Optimize
- run_autotune — Assisted tuning across modes such as hashrate, efficiency, watts, and temperature targets
- ota_check — Check for and apply firmware updates
- restart_mining — Clean restart of the mining pipeline
- get_swarm — Multi-miner fleet coordination
Resources
- bitaxe://status — Real-time miner state as structured data
- bitaxe://history — Rolling performance history
- bitaxe://config — Current configuration snapshot
Example target workflow: “Set my Bitaxe Gamma to best efficiency mode and lower the fan target.” Actual commands, supported ranges, and safeguards will depend on the beta build installed.
Agentic Mining: Automation With Guardrails
The MCP work is intended to make BitAxe miners easier to automate without hiding what the firmware is doing. Compatible agents could eventually read telemetry, propose tuning changes, switch profiles, and coordinate small fleets through explicit tool calls instead of screen scraping or fragile scripts.
That matters for miners who want repeatable optimization: heat-aware schedules, efficiency targets, pool monitoring, donation routing, and alert-driven recovery can all be exposed as controlled workflows. During beta, D-Central will prioritize visibility, operator approval, and documented limits over unchecked autonomy.
For Bitaxe owners, the practical goal is simple: keep control local, make actions inspectable, and let advanced users build automation on top of open interfaces. The miner owner still controls the hardware, firmware, pool credentials, and payout address.
Target Agent Workflows
- Monitor a miner — Read status, shares, temperatures, power state, and network health
- Recommend tuning — Suggest frequency, voltage, and fan changes within documented ranges
- Manage profiles — Switch between heat, mine, and hack-oriented operating modes
- Coordinate fleets — Compare multiple BitAxe devices and flag outliers
- Explain actions — Keep changes visible so operators understand what happened
Compatible Agent Frameworks
- OpenClaw — Autonomous AI agents with tool use and wallet integration
- NanoClaw — Lightweight agents optimized for embedded and IoT control
- Claude Code — Anthropic’s CLI agent with native MCP support
- Any MCP client — The protocol is open; build your own agent and point it at your BitAxe
Bitcoin mining automation should be transparent. DCENT_axe is being designed so agents assist the operator without hiding the operating state of the miner.
DCENT_axe vs Stock AxeOS
Skot and the entire ESP-Miner community built the foundation that made DCENT_axe possible. We used ESP-Miner as our protocol reference, and we are grateful for every line of open-source code and every register map they published. DCENT_axe exists because AxeOS proved that open-source BitAxe firmware works. We are building on the shoulders of giants. DCENT_axe is a complementary option that adds features on top of a Rust foundation, giving BitAxe owners more choice. More options means more decentralization.
| Feature | Stock AxeOS | DCENT_axe Beta Target |
|---|---|---|
| Language | C | Rust firmware track |
| AI Control (MCP) | No | 12+ planned tools, 3 planned resources |
| Stratum V2 | No | In development |
| Autotuner Modes | Basic | Hashrate, efficiency, watts, and temperature targets |
| OLED Display | Static stats | Expanded display workflow target |
| Achievements | No | Milestone tracking target |
| Luck Calculator | No | Solo-mining probability target |
| Mining Pause | Requires reboot | Soft pause target |
| Pool Failover | Single pool | Multi-pool failover target |
| Persistent History | Lost on reboot | Persistent history target |
| Silicon Grading | No | Chip-grade reporting target |
| Home Assistant | No | MQTT integration target |
| Web Dashboard | Basic | Dashboard target with stronger controls |
| OTA Updates | Yes | Planned after beta recovery paths are stable |
| License | GPL | GPL-3.0 public release target |
Before You Flash
Public beta firmware is for testers who accept real hardware risk. Confirm your exact BitAxe model, chip family, board revision, current recovery method, release notes, and checksum before installing anything. If that sounds like too much, wait.
- Use a test miner, not irreplaceable production hardware.
- Keep a known-good AxeOS recovery image and the right cable nearby.
- Expect unstable behavior, incomplete features, and possible downtime.
- Do not flash a build marked for another chip family or board revision.
- Check this page and the flash page again before every beta attempt.
Getting Ready for DCENT_axe
The public beta is being staged. Use this checklist to prepare, not as permission to flash unsupported hardware.
Step 1: Wait for a Matching Image
DCENT_axe public images are support incoming. When a build is posted, it will be tied to a model, chip family, and hardware revision. Join Discord or check this page for release notes and compatibility updates.
Step 2: Read the Release Notes
Before using OTA or the DCENT firmware flash page, confirm that the release notes list your exact hardware, known issues, recovery method, and checksum. Browser flashing will require USB-C and user-selected confirmation.
Step 3: Prepare Recovery
Have a known-good firmware image, USB cable, and any serial/UART recovery steps ready before testing. If the beta fails to boot or join WiFi, recovery may be manual.
Step 4: Configure Carefully
When public beta builds are available, start conservatively. Confirm WiFi, dashboard access, pool configuration, thermals, fan behavior, and share acceptance before increasing frequency or voltage.
Step 5: Connect Your AI (Optional)
MCP control is optional and experimental. Start with read-only status checks where available, then enable control tools only after you understand the operating limits of that beta build.
Step 6: Report What Breaks
Public beta only improves if testers report hardware model, board revision, logs, recovery outcome, and the exact build used. Treat every beta flash as a test session.
Under the Hood
For the technically curious. DCENT_axe is a Rust workspace with modular crates — each responsibility isolated, each interface clean.
Architecture
- dcentaxe — Main binary and entry point
- dcentaxe-asic — ASIC drivers (BM1366, BM1368, BM1370, BM1397)
- dcentaxe-hal — Hardware abstraction: UART, I2C, power, fan, GPIO, temperature
- dcentaxe-stratum — Stratum V1 client with version rolling
- dcentaxe-mining — Work dispatcher, nonce validation, statistics
- dcentaxe-stratum-v2 — Stratum V2 with Noise protocol (optional feature flag)
Technical Specifications
- Platform: ESP32-S3 (xtensa-esp32s3-espidf)
- Framework: ESP-IDF v5.3+ via esp-idf-sys
- RAM Usage: ~180 KB of ~300 KB available
- Dashboard: ~60 KB gzipped inline HTML/CSS/JS
- Display: 128×32 SSD1306 OLED via I2C
- Temperature: EMC2101 sensor
- Power Monitoring: INA260
- Voltage Regulation: TPS546, DS4432U
- Fan Control: 25 kHz LEDC PWM
- Protocol: Stratum V1 + ASICBoost (V2 in progress)
Roadmap
DCENT_axe is under active development. Here is what is coming next — built by miners, for miners.
Coming Soon (v0.3 – v0.5)
- Full Stratum V2 integration with encrypted mining
- TLS/SSL encrypted pool connections
- mDNS discovery (bitaxe-XXXX.local)
- Voltage curve optimization and undervolting
- Home Assistant MQTT with auto-discovery
- Discord and webhook notifications
- Scheduled mining profiles (time-based power management)
- Hashrate splitting across multiple pools simultaneously
- Pool-side statistics integration
- Dashboard authentication with optional PIN
Future (v0.6+)
- WebSocket real-time stream for instant share notifications
- Prometheus and Grafana metrics endpoint
- Shareable mining card (SVG/PNG with QR code)
- Context-aware thermal management guidance
- WiFi signal quality monitoring
- First-run setup wizard
- Firmware signature verification (Ed25519)
- API rate limiting
- Achievement gallery with visual unlock progression
Frequently Asked Questions
Is DCENT_axe free?
DCENT_axe is planned for a GPL-3.0 public release after the beta period. The target is no mandatory hidden dev fee, no subscriptions, no locked features, and no telemetry. If optional contribution routing is offered, it should be visible and user-controlled.
Will DCENT_axe brick my BitAxe?
Yes, it can. Any beta firmware can leave a miner unbootable, misconfigured, or in need of recovery. Only install DCENT_axe on hardware you are prepared to debug, recover, or temporarily lose. If you are not ready to FAFO, wait for a later release.
Which BitAxe models are supported?
The beta track targets BM1370 (Gamma, GT), BM1366 (Ultra, Hex Ultra), BM1368 (Supra, Hex Supra), and BM1397 (Max). Support is not automatic. A matching public image must exist for your model, board revision, sensor set, and power monitor before you flash.
Do I need an AI assistant to use DCENT_axe?
No. MCP is optional. The target experience includes a web dashboard and AxeOS-compatible REST API behavior for normal operation, with AI-assisted control available for miners who explicitly enable it.
What is the MCP server?
MCP (Model Context Protocol) is an open standard for AI tool integration. The planned DCENT_axe MCP server exposes miner status and selected control operations as documented tools and resources so compatible clients can monitor, tune, and automate with clearer permissions.
Does DCENT_axe support Stratum V2?
Stratum V2 support is in active development. Public beta release notes will state which mining protocol features are enabled in each build. Do not assume Stratum V2 is production-ready until the release notes say so.
Can I use DCENT_axe for solo mining?
Solo mining is a target workflow through standard Stratum V1 pool compatibility, including solo mining pools where supported. Confirm pool behavior in the release notes for the build you install.
How does the Tamagotchi work?
Your OLED display shows a pixel-art creature that evolves through six stages (Egg, Hatchling, Miner, Veteran, Legend, Titan) based on real mining milestones. There are 16 achievements to unlock. The creature’s mood reflects your miner’s health — happy when hashing, sad when offline. It is a fun way to stay connected to your miner without staring at dashboards.
Is DCENT_axe compatible with the AxeOS REST API?
AxeOS-compatible REST API behavior is a design target. Beta builds may have gaps or changed behavior, so integrations should be tested against the specific release you install.
Who builds DCENT_axe?
DCENT_axe is built by D-Central Technologies, the same team that has been supporting Bitcoin miners since 2016 through ASIC repair, refurbishment, hosting, parts, and open-source mining hardware support in Canada.
BitAxe Miners – DCENT_axe Target Hardware
