Hardware online
0 / 0Waiting for your first connection
CM CRYPTOMINER CONTROL CENTER
Fleet overview
Keep every machine in view. Put idle compute to work.
YOUR HARDWARE. YOUR REWARDS.
Every machine.
One clear view.
Monitor performance, follow rewards, and manage your fleet.
Estimated daily earnings (BTC equivalent)
0.00000000 BTCLive rates · excludes electricity
Confirmed pool balance
— BTCConnect your pool account
Estimated contribution
0.00000000 BTCObserved time only · not pool credit
Fleet performance
Measured hashrate · observed samples over 24 hours
—current primary-algorithm rate
24 hours ago12 hours agoNow
Hover or focus a sample to inspect it.
At a glance
Each square is one connected worker
MiningIdleOffline
Mining right now0 machines
Your hardware
Live status, estimated earnings, and controls for each PC
✓ Your wallet stays yours. The dashboard uses your public receive address. Recovery phrases and private keys are never needed.
Connected machines
Commands queue until a worker checks in. Start commands expire after ten minutes.
0 selected
Per-machine earnings are estimates from measured performance and fresh pool yields. Confirmed individual credits are unavailable unless your pool reports them. Pool balances are never divided into invented worker earnings.
Your payout destination
BTC · native Bitcoin network
₿
Bitcoin receive address
Mining rewards accumulate at the pool. Payouts depend on its minimum, available balance, processing schedule and network. A submitted request is not a confirmed deposit.
Before your first payout
- Attach the BTC mining address to your unMineable account.
- Connect your account API credentials and mining alias here, or choose legacy address mode.
- Sync your pool balance, review the full destination, then approve a request.
Payment history
Pool has not been synced
Inspect the provider’s raw balance response
No pool data available.
Headless service workers: install a newer CMcryptoMiner-Setup.exe on each PC to update. Remote release deployment and benchmarking below are for desktop workers.
Worker releases
Upload a built worker executable, approve its SHA-256, then deploy it to selected hardware.
Workers fetch approved releases from this server, check the digest, stop mining and use their packaged updater to replace the worker. Engine updates use official miner releases. System security decisions remain in force.
Command history
Queued, delivered, completed and failed actions