Official FutureBit Apollo II/BTC Software/Image and Support thread

[NotFuzzyWarm]

Why no exchange addresses? Mine on coinbase are native segwit. Only catch I can think of is that some exchanges may not like new coins and would question where the coins came from and freeze them until explained. FYI, Coinbase has no issues with that.

[btcdfghj]

As someone who has won a block using a “bc1q….”  address, I can vouch that Native SegWit address are good. If you use an invalid address I’m pretty sure ckpool will reject the connection.

Thank you! Good to know that Native Segwit addresses are ok for solo mining using FutureBit node hardware&software. Congrats to you on your winning the block!

[btcdfghj]

Hi guys,

I've got a question regarding FutureBit Solo Node Solo Mode Configuration setup.

The official Solo Node Guide (which is included in the Solo Node files) says (in the "Solo Mode Configuration"):

"Please note only legacy or legacy segwit addresses are supported for solo mining currently. DO NOT USE EXCHANGE ADDRESSES FOR SOLO MINING".

I get the part about the exchange addresses but what is a "legacy segwit address" ?

Do "bc1q........" type addresses qualify for solo mining on FutureBit Solo Node?

my guess is that needs to be upgraded to include bc1q***   addresses

ie :

legacy. begin with 1
legacy segwit begin with 3
native seqwit begin with bc1q

no exchange addresses

only 90 to 95% sure I am correct

Got it, so Legacy Segwit is just another name for Nested Segwit.

I guess that part of the Solo Node Guide is copy-pasted from an outdated Apollo Node guide then, and should be corrected to include Native Segwit as well.

[Block888737]

I ran the test script that Atlas Pool provides against my Solo Node, and it looks like you can even use Taproot if you want to.

https://www.talkimg.com/images/2026/05/19/UVfOcC.jpeg

[btcdfghj]

I ran the test script that Atlas Pool provides against my Solo Node, and it looks like you can even use Taproot if you want to.

https://www.talkimg.com/images/2026/05/19/UVfOcC.jpeg

I've tried to insert a really long random address into the SOLO settings field on my Solo Node (with the latest v2.1.1 firmware) and got a warning while typing the 62nd character:

"Warning: P2WSH and P2TR Bitcoin address are not valid for SOLO mining. Please add a different Bitcoin address"

P2WSH is a specific address type which starts with "bc1q...." but is 62 characters long (as opposed to Native Segwit "bc1q...." type address which is 42 characters long).

P2TR is a Taproot address which is 62 characters long as well.

So it looks like Native Segwit addresses ("bc1q...." which are 42 (not 62!) character long) are good for Solo mining on FutureBit Solo Node currently, and the guide contains outdated information.

Reference chart of Bitcoin address types:

https://www.unchained.com/blog/bitcoin-address-types-compared#reference-chart

[bubbAJoe]

1,642,829,444,856 from my Apollo II.  Only need about 80x more, LOL!!!

[jstefanop]

Apollo OS 2.1.2 is pushed to wide release.

Go to your web UI refresh and power button should have the new update available!

Changelog:

•⁠  Overview UI now shows additional power/temp/pool graphs
•⁠  ⁠mindiff (solo "Minimum Difficulty", default 1, added to solo pool settings), useful to control incoming shares per second if connecting with really high rental hashrate with large number of devices
•⁠  ⁠Knots 29.3 (v29.3.knots20260508) added to node client software
•⁠  ⁠Core: 31.0 added to node client software
•⁠  ⁠New node software selector UI (grouped Core/Knots version badges instead of the dropdown)
•⁠  ⁠Real-time WebSocket subscriptions (replaces polling) + reliability fixes:
  Core warmup treated as online, multi-device connectivity, null-safe settings, node data kept on transient errors
•⁠  ⁠Misc UI: 2x2 metrics grid, circle flags, login redirect fix


We are no longer issuing images for every point release due to the large number of supported devices. If OTA update fails reflash the last available image and try the update again.

Quicker method to recover a failed update is to SSH or log into your desktop, open terminal window and redo the update with:

cd /opt/apolloapi/backend

sudo ./update

We are working on OS 2.2 which will be a major architectural  revamp, and allow for nearly faillproof OTA updates as well as the ability to release at a faster cadence.

We have a lot of cool features in the works for the rest of 2026 and our focus will be on the OS/feature list after the Apollo III launch!

If you guys have feature requests post them here!

[BlazeB]

Thank you for the update. I'm looking forward to getting my Apollo III.

Feature requests:

Off-peak scheduling – Ability to schedule the miner to run during off-peak electric rates (know this is already planned for 2.2)
Solo pool hashrate display – Show solo pool hashrate graph when a miner is connected to the solo node
Worker screen layout – Rework the Solo Pool screen to show multiple workers without scrolling; there's a lot of empty space, and once you get past 3–4 workers it requires a lot of scrolling
Alerts – Discord or Telegram notifications for best new shares

[heslo]

Thank you for the update. I'm looking forward to getting my Apollo III.

Feature requests:

Off-peak scheduling – Ability to schedule the miner to run during off-peak electric rates (know this is already planned for 2.2)
Solo pool hashrate display – Show solo pool hashrate graph when a miner is connected to the solo node
Worker screen layout – Rework the Solo Pool screen to show multiple workers without scrolling; there's a lot of empty space, and once you get past 3–4 workers it requires a lot of scrolling
Alerts – Discord or Telegram notifications for best new shares

Yep scheduling would be great! Definitely a feature I would use!

[btcdfghj]

Quicker method to recover a failed update is to SSH or log into your desktop, open terminal window and redo the update with:

cd /opt/apolloapi/backend

sudo ./update

Hi guys,
I've tried this after a failed update to 2.1.2 on my Solo Node and it wouldn't start the update.

[jstefanop]

Thank you for the update. I'm looking forward to getting my Apollo III.

Feature requests:

Off-peak scheduling – Ability to schedule the miner to run during off-peak electric rates (know this is already planned for 2.2)
Solo pool hashrate display – Show solo pool hashrate graph when a miner is connected to the solo node
Worker screen layout – Rework the Solo Pool screen to show multiple workers without scrolling; there's a lot of empty space, and once you get past 3–4 workers it requires a lot of scrolling
Alerts – Discord or Telegram notifications for best new shares

Yep scheduling would be great! Definitely a feature I would use!

Those are all being actively developed for 2.2! (except alerts will look into that).

[jstefanop]

Quicker method to recover a failed update is to SSH or log into your desktop, open terminal window and redo the update with:

cd /opt/apolloapi/backend

sudo ./update

Hi guys,
I've tried this after a failed update to 2.1.2 on my Solo Node and it wouldn't start the update.

Make sure they are two seperate commands, terminal should show some type of output even if it fails if you started it correctly.

[btcdfghj]

Quicker method to recover a failed update is to SSH or log into your desktop, open terminal window and redo the update with:

cd /opt/apolloapi/backend

sudo ./update

Hi guys,
I've tried this after a failed update to 2.1.2 on my Solo Node and it wouldn't start the update.

Make sure they are two seperate commands, terminal should show some type of output even if it fails if you started it correctly.

I did but there was no output.

https://imgur.com/a/X5wgYWz
https://imgur.com/a/nsTKHrX

I've also wanted to reflash my Solo Node back to 2.1.1 image with the SD card method but wasn't able to get the SD card out of the Node - pressing it inside doesn't move it a bit, trying to simply pull it out without pressing in doesn't seem to work either. Afraid of breaking the SD card socket, not sure how to do it properly.

[BlazeB]

Hi guys,
I've tried this after a failed update to 2.1.2 on my Solo Node and it wouldn't start the update.

Make sure they are two seperate commands, terminal should show some type of output even if it fails if you started it correctly.

I did but there was no output.

https://imgur.com/a/X5wgYWz
https://imgur.com/a/nsTKHrX

I've also wanted to reflash my Solo Node back to 2.1.1 image with the SD card method but wasn't able to get the SD card out of the Node - pressing it inside doesn't move it a bit, trying to simply pull it out without pressing in doesn't seem to work either. Afraid of breaking the SD card socket, not sure how to do it properly.

It is odd that there is no output; it might be easiest to reflash. I, too, had the issue with the SD card on my Solo Node. I'm not sure if there is supposed to be a spring mechanism, but I ended up using needle-nose pliers to gently pull mine out.

[btcdfghj]

I did but there was no output.

https://imgur.com/a/X5wgYWz
https://imgur.com/a/nsTKHrX

I've also wanted to reflash my Solo Node back to 2.1.1 image with the SD card method but wasn't able to get the SD card out of the Node - pressing it inside doesn't move it a bit, trying to simply pull it out without pressing in doesn't seem to work either. Afraid of breaking the SD card socket, not sure how to do it properly.

It is odd that there is no output; it might be easiest to reflash. I, too, had the issue with the SD card on my Solo Node. I'm not sure if there is supposed to be a spring mechanism, but I ended up using needle-nose pliers to gently pull mine out.

Thank you for your reply. I've managed to pull the SD card out carefully (without pressing it in beforehand) and reflash the Node with the 2.1.1 image. Now trying to update again using the Web UI.