Home mining,
at a glance.

Your home ASICs (Bitaxe, Gamma Hex included, NerdQAxe and Naja Duo on AxeOS, Avalon, Hammer on ThorOS, the GekkoScience KBox, Zyber on ZyberOS, and any rig running Harlo-OS) on your LAN, plus your solo pool wallets across BTC and BCH. It tracks hashrate, best share and block odds, worker status, temperatures, pool stats and network difficulty.

Send us its readings and we'll work on it. In the app, tap + on the Hardware tab, then Miner not listed? Help us add it, under the Add device button. The network scan has the same button. If SoloDeck already reads your miner but gets its name or a stat wrong, use Send readings on the miner's page instead.

SoloDeck asks the miner what it knows, only reading and never changing anything, then takes out your wallet, passwords, Wi-Fi name, serial numbers and network addresses before it writes the file. Nothing is uploaded: the share sheet opens, and you send the file to support@solodeck.app. It's free.

Yes. SoloDeck reads thirteen pool families and shows them all in one place; the full list is under Features. More will be added over time. If you run a pool, or want yours added, here is what SoloDeck needs from its API.

Yes, and only for home miners. It's built for hobbyists running a handful of ASICs at home on solo pools, not for farm-scale operations.

SoloDeck is on the App Store for iPhone and iPad, and needs iOS or iPadOS 15 or later. On an iPad it puts the list and the page you picked side by side.

It also runs on a Mac with Apple silicon (M1 or later) and macOS 26 or later. Get it from the App Store on your Mac. It's the iPad layout in a window you can resize, and it finds the miners on your network the same way.

It's one app, so Premium covers all of them with the same Apple ID. If it doesn't show on another device straight away, open the Premium screen and tap Restore Purchases.

Android is planned, but there's no date for it yet.

No. Each install keeps its own rigs, wallets, settings, charts and cost history, and nothing syncs between them. There's no account, so there's nowhere for it to sync through.

Premium does carry over. On the second device, open the Premium screen and tap Restore Purchases, signed in with the same Apple ID.

To set up the second device the same way, go to Backup in Settings, tap Save to a file on the first device and Restore from a file on the other. The file holds no passwords, so you type those in again. Backup and restore is part of Premium.

Alerts follow the wallets on each device, so a wallet added on both sends its alerts to both.

Yes. They're cloud-delivered push notifications, so they reach you even when the app is closed. Four event types: Block Found, New Best Share, Worker Offline and Worker Online. Block Found and Best Share are free; the other two are part of Premium. There's a page on how alerts work with the timing and the pool details.

First, SoloDeck is not a node and doesn't run one. It reads a node you already run at home, on an Umbrel or a computer of your own. Your phone can't be the node either: a node runs around the clock, keeps the whole blockchain, which is hundreds of gigabytes, and takes connections from your miners, while iOS pauses any app you're not looking at.

Open the My Bitcoin Node tab and fill in five fields. It works with any Bitcoin Core or Knots node whose RPC answers on your own network, Umbrel or a build of your own, sitting behind a self-hosted Public Pool.

The address is your box's address on your home network, and it's the same one for both the pool field and the node field. Your router's device list has it, so does the Umbrel dashboard.

The pool port is whatever serves your pool's own web page: 2019 on Umbrel's Public Pool, 3334 if you installed it by hand. The node port is Bitcoin Core's RPC, usually 8332.

On Umbrel, the RPC user and password are in the Bitcoin Node app's connection details, the ones it shows you for connecting wallets. The user is normally umbrel and the password is long and random, so paste it. Reinstalling the Bitcoin app generates a new one. Don't look in bitcoin.conf. It stores a hash of the password, never the password.

To reach it from outside the house, set up a Tailscale subnet route and keep entering your normal home address rather than a Tailscale 100.x address.

Your credentials are held in the iOS keychain on your phone and are never sent to us. Premium.

Your phone reached the node, but Bitcoin Core turned it away before it looked at the password, so the password isn't the problem. Core only answers addresses on its allow list, the rpcallowip lines in bitcoin.conf, and your home network isn't on it yet. Your pool has no such list, which is why the page can still say Connected while the node is unreachable.

First, work out your home network range. Your phone only shows its own address, so on your home Wi-Fi with any VPN off, open Settings, then Wi-Fi, tap the i next to the network and look at IP Address. Replace the last number with 0/24. So 192.168.1.80 becomes 192.168.1.0/24.

On Umbrel, open Terminal on a Mac or PowerShell on Windows, on your home Wi-Fi, and sign in to the box with your Umbrel password:

Paste this with your own range swapped in, then the second line to restart the Bitcoin Node app:

It has to be bitcoin.conf. Umbrel rewrites umbrel-bitcoin.conf itself, so a line added there is lost.

On a node you built yourself, add the same line to bitcoin.conf and restart Core. If you set rpcwhitelist, a call missing from it gets this same refusal.

Don't use 0.0.0.0/0. It lets any address try your RPC password. The new line only adds your home network to the list, so reaching the node through Tailscale keeps working.

Without one, SoloDeck uses the wattage each miner reports. That's what the firmware thinks it draws, and it leaves out what the power supply loses, so it reads a little under the wall. A metering plug measures at the socket, so the losses are in the figure.

A plug also covers the hours the app was closed. Without one, SoloDeck averages the draw it saw and carries it across the time it didn't, and the app marks that figure as an estimate. A plug keeps its own energy counter, so SoloDeck reads the real total the next time it looks.

Cost is worked out from the energy when you look, so changing your kWh price re-prices the whole history. On a night tariff, set both rates and their hours, and each stretch is priced at the rate that applied.

A Shelly or Tasmota plug can also power cycle a rig that's stuck. SoloDeck sends the plug one command: switch off, then back on after 10 seconds. The plug does the switching on itself, so a phone that drops off Wi-Fi halfway can't leave the rig off. Everything on that outlet goes off for those 10 seconds, so the confirm names every rig behind it. Tasmota needs firmware 13.4 or newer for this, and a plug read through Home Assistant can't do it.

Plug reading, the power cycle and the cost history are Premium. Which plugs work is in the smart plugs section.

A Shelly or Tasmota plug needs no pairing. Run the scan on the Hardware tab and the plug appears under Smart plugs at the bottom of the list. Tap it, tick every rig plugged into it, and SoloDeck starts counting. Plugs that don't meter power aren't listed.

For anything else, use Home Assistant. Add a Home Assistant meter and give it the server's address (usually port 8123) and a long-lived access token. To make the token, click your name at the bottom left in Home Assistant, then Security, then Create token. SoloDeck lists the plugs Home Assistant can see: pick yours, then its power sensor and its kWh total. The token is stored in the iOS keychain.

Before you buy: SoloDeck reads one outlet per plug, so on a metering power strip it only reads the first. And a Shelly or Tasmota with a web password can't be read directly; clear the password or go through Home Assistant.

SoloDeck records while it's open. Every refresh feeds the 24 hour chart, and the longer ranges keep one reading per 15 minutes so a year of them still fits on your phone. Nothing is recorded on a server for you.

Time the app spent closed leaves a hole in those readings. The line draws straight through so the chart stays easy to read, and the caption under it tells you how much was actually recorded: as hours and minutes on the 24 hour chart, and as a share of the range on the longer ones. The average beside it only uses the recorded stretches, not the gaps.

24 hours is free and stays on your phone. The 7D, 30D and 1Y ranges are Premium, and they fill from the day you switch them on, so a new subscriber's year is empty at first.

A fleet total only counts the rigs that answered. If two miners miss a refresh, that point would read as a crash that never happened, so it's dropped and the line carries on past it. Switching a rig off for good is a real change, and that stays on the chart.

Premium can export the whole history to a text file from Settings.

The Efficiency figure on the Fleet page is the fleet's total watts divided by its total hashrate. Each rig counts in proportion to the hashing it does. Averaging the rigs' own J/TH figures would let a small rig count as much as a big one.

Take an Avalon Q doing 90 TH/s on 1,674 W (18.6 J/TH) and a Bitaxe doing 1.2 TH/s on 18 W (15 J/TH). Together that's 1,692 W for 91.2 TH/s, so 18.6 J/TH. An average of the two would say 16.8, as if the Bitaxe did half the work.

It uses the wattage each miner reports, so it leaves out what the power supplies lose. A rig that doesn't report its power is left out of both totals.

Pool stats and alerts work from anywhere. LAN features like ASIC auto-discovery and direct miner control run while you're on the same network as your rigs.

There's a free way to make those work from anywhere too, and with an Umbrel it takes about 15 minutes to set up: follow the step-by-step guide.

Free covers one wallet, up to ten miners on your network, 24 hours of charts, Block Found and Best Share alerts, and the small widget.

Premium is $3.99/month, or $29.99/year with a 7-day free trial. It lifts both limits to unlimited, and adds the My Bitcoin Node tab, smart plugs with what the fleet costs to run and a power cycle for a stuck rig, a year of chart history with export, backup and restore, the other two alerts with custom thresholds and quiet hours, and the medium and large widgets.