I got both (MCU1 and Apollo II S) sending data at the same time to NiceHash by using "stratum+tcp://sha256asicboost.auto.nicehash.com:9200" instead of stratum+tcp://sha256.auto.nicehash.com:9200. However they do appear to be inversely labeled as displayed on the "Hashboards and Pools" page.

Use it as a hardware wallet for your mining or solo mining address.

We included it for new users that dont have wallets so they can get started in one step by just importing the wallet address for either solo mining or mining straight to wallet address using ocean pool.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?

Hello all.  I have one of the full node Apollo 1 machines and just got my Apollo II Standard to plug into the original Apollo and increase my hashrate.  I have followed the instructions that came with the machine and it does not appear to be increasing the hashrate of my original device in the mining pool.  Is there something else that needs to be done so that the two units will work together?  I know a new OS is coming out soon for the old machines but as of now, it doesn't seem like the original Apollo BTC Full Node is using the new Apollo II standard for any work.  Any help would be appreciated.

Not sure where you are coming up with this, we respond to every email and im looking at our support que right now and there are only 10 outstanding tickets that will probably be answered in the next few hours (and we only have queues after weekends).

So if your definition of non existent support means not answering your immediate question within 10 minutes, then yes we have non existent support and will continue to have non existent support. Im not hiring random support agents from India and driving up costs of our units by 20% to satisfy this urge.

All our support emails are answered by my team that work on the units themselves (including myself) and can actually answer your question, but this means you might not have a response for a few days.


Now in terms of the nodes issues we are not seeing anything on our test systems, nor any widespread outages (my first thought was the ordinals/BRC-20 fiasco causing issues, but even with 1G mempool we have plenty of memory overhead).

Second issue could be if you have a recent system (bought after Nov/Dec last year), we switch to a new controller heatsink and some units were assembled without the heatsink adhesive properly installed. If your node/system is shutting down, or your your MCU temp (the one on the top menu bar) is higher than 85c then this could be the issue. You'll need to remove the side panel the MCU is on and remove the MCU and reseat the heatsink (press down on it hard for at least 10 seconds to make sure the thermal pad is stuck on there well).

Second step if your still having an issue is to reflash your SD card to make sure there is no corruption that could be causing system instability, if your still having node issues email us with two below logs:

take a screenshot of system monitor while the node is still active (preferably after it has started up and synced), you can open a terminal and type htop for this
send log file of bitcoind, its in the Bitcoin folder inside the node drive (debug.log)

Does the issue persist? Have you tried rebooting after those updates?
You can replace my bitcoin user with futurebit, yes. Technically, in my setup, that user is less privileged so it's a little bit more secure, but it's still fine.

I run the latest Futurebit OS and when I run those commands to upgrade the miner stops working. I can only get it working again by reflashing the card.

I don't use Ledger Live, but it seems that such a bridge is required, yes. You could also just use a better Bitcoin wallet software like Electrum or Sparrow and connect your Ledger to that software.

First of all, you have a web GUI; so the miner dashboard that you get when connecting a screen to the Apollo, is also displayed by visiting the miner's IP from any browser in the same network.
To 'interact with the blockchain' in terms of querying blocks and stuff like that, indeed installing electrs is what's going to allow you to do that.

If you run the latest Futurebit OS, you can do the updates via:

Just don't do distro-upgrades like sudo apt dist-upgrade. Don't do that!

Trezor Suite allows you to choose a custom Electrum server.


You can install such an Electrum server on the Futurebit Apollo BTC, no problem.
Here are my instructions. They are for a full custom Linux install, but work on stock Futurebit OS, as well. Just follow the electrs instructions.

Internet connection monitor shows 0 drops in connection since I last posted. The miner also never stopped during that time so it may have been some internet dropouts in the past that caused it indeed.

Thanks I will try that. Internet is pretty good but if there are small drop outs I may not notice. The LTC miner does not stop though and the BTC node either.

short versions of the log in chrome

 note: 208 dropouts








sample of the log
and I highlighted the 30 second plus one that stopped the miner

CPU usage during block sync is directly related to your bandwidth. During our tests we were maxing out the CPU at around 5-10 MB/s.

Will check out MRR, didn’t do any testing on that pool.

CPU usage during block sync is directly related to your bandwidth. During our tests we were maxing out the CPU at around 5-10 MB/s.

Will check out MRR, didn’t do any testing on that pool.