More technical and in-depth information:ControllerAs I found out when making my
[Custom Linux install guide for the Futurebit Apollo], it was hard to find OS binaries for this SBC. It comes with
Debian Armbian, and that's what I ended up using for my custom install (see below), as well. It's not OrangePi's fault, but the community support is also much worse than anything from RaspberryPi (less discussions, forums, and support sections), so if you're a newbie and want to tinker with it, you can't really find ready-made instructions for anything online. Well, of course now,
there are mine.
I do have to say I find it a bit dishonest (as I alluded to earlier) how Futurebit claim it's
their controller, purposefully cease to mention the SBC used and even
claim it's as fast as any(!!!) desktop computer. Such a claim can be refuted by pointing out a single desktop computer that is faster, so I'd be very careful with absolute claims. Even if they claimed it was
as fast as a desktop computer, it would be wrong. They probably refer to the chip having 6 cores, which is not too shabby by today's home computing standards, but core count alone doesn't paint the whole picture.
In my experience, it feels around as fast as a Raspberry Pi 4, and definitely much slower than any of my nodes, even easily beat by an
upgraded laptop node. I think I paid around $150 for that whole node since I upgraded to a 1TB SATA (NVMe has no real-world performance benefit for a node) SSD and 8GB of RAM. But the processor is a super old Celeron dual-core.
Compile times on the Orange Pi are so long
that I resorted to pulling a compiled binary for Bitcoin Core.
The CPU even overheated after a while and I had to reboot and retry. After two attempts, I just got the binary release.
It's important to point out (as seen in the pictures), that the fan cooling the SBC is pulling in air from
below the hashboard. It works fine in normal operation, but I would personally have turned it upside down so it can get fresh air instead. The fan is also not silent - it's a 40mm, pretty cheap looking fan and for silence I'd replace it. Especially when it's not mining (more on noise later).
All the critiques out of the way though, the controller
does run the 'whole Bitcoin software stack' that it's advertised to run, even though you have to
manually install everything and there's been no offical guide,
until I made my own, even after
repeated questions in the support thread ........Full Node Info
The Apollo Full Node runs the latest release binaries from bitcoincore.org, and is automatically configured and setup at the system level. It will start syncing a clean chain state from block 0 on your nvme SSD on first boot, and is capable of downloading a full unpruned node on its 500 GB drive with a 1-2 year buffer. This is the core that will enable us to release additional apps and services in the coming months and years (solo mining, block explorer, Lightning network all planned in the short term), and allow you the user to verify your own transactions and chain state without needing to trust anyone else.
This message is around 13 months old now; there is no block explorer, LN or solo mining so far and since it's included in the quote I'd like to point out that batch 1 and 2 shipped with a 500GB drive, which was obviously too small and did not have a 1-2 year buffer at all. I recently switched a node from 500GB to 1TB, even though I already had pulled indexes and chainstate off the 500 gig drive. So I'd say the time where 500GB was enough for a full node, has passed less than 1 year after that message.
Of course, the blockchain is not yet over 500GB, but with chainstate and additional files, the Bitcoin directory is now at almost (or over) 500GB. It's good that they now ship these devices with 1TB drives; that's enough headroom for all the extra software, too.
orangepi4:admin:# du -ch /media/nvme/Bitcoin/blocks/blk*.dat | tail -n1
385G total
[Theoretical blockchain size: 385GB]orangepi4:admin:# du -ch /media/nvme/Bitcoin
109M /media/nvme/Bitcoin/blocks/index
437G /media/nvme/Bitcoin/blocks
4.7G /media/nvme/Bitcoin/chainstate
442G /media/nvme/Bitcoin
442G total
[Practical Bitcoin blockchain folder size: 442GB]Noise / is it quiet?The subject of noise is pretty important to me. It is my main motivation for getting pod and stick miners instead of industrial ones. I like the cooling design of the hashboard. But if you've got some experience with CPU wattages and what heatsinks are required to cool 200 or even 300 Watts, it will be no big surprise to you that a single 95mm fan can't
silently cool off +200W of energy.
- There is a large heatsink on top of the 44 ASIC chips with slender poles sticking upwards. On top we have a static-pressure fan that pulls air through the heatsink and ejects it up top. It wasn't clear to me prior to buying it and it makes a lot of sense.
- If you run the unit in ECO mode, it's pretty quiet and you can have it in the same room you're working in, without really noticing. However I don't like the idea of 'leaving performance on the table'.
- Even in balanced mode, it's pretty loud (to me). I tried to sit it on something rubbery and even sound-absorbing foam, to no avail.
- The way I managed to run it silently (!) in balanced and quiet in turbo mode was to sit the whole unit on top of a 140mm PC fan, blowing air upwards, as well as a 120mm PC fan just sitting on top of the unit, blowing upwards as well. I hooked them up to one of the Pi's USB ports (5V), so these 12V DC fans run at just below half speed. They are really quiet at this speed and help the builtin fan so much that it tunes itself down automatically. It's easy, cheap and quick to do (if you already have the components) and in case your solder job is bad or for something catches those external fans, the internal one can still rev up and cool the unit down, so not to melt your place. I'd be very cautious about other modifications, such as changing the internal fan's fan curve or replacing it. This way you always have a potent fallback.
Software- The web GUI works fine. It was easy to get up and running quickly.
- I noticed that even though I changed the GUI and SSH passwords, somehow I couldn't log back in after a few months; it was back on the default (futurebit123). No idea why, but a little scary.
- As mentioned above, you get Bitcoin Core and the miner + web GUI - that's it. I really miss Electrum and Lightning on this, because that's what I use daily and gives me a tangible, real-world benefit. If you just want to mine, get the 'only miner' option (you can 'help the Bitcoin network' for $50 if that's what you're after).
- jstefanop recommends not to update the operating system (sudo apt update && sudo apt upgrade), because it may break stuff. This is pretty unacceptable to me, as the easiest way that hackers get into a network / system is looking for outdated packages and misconfigurations. It's definitely easier than looking for 0-days yourself!
- Using the built in system update function will brick your system DO NOT UPDATE USING THE SYSTEM UPDATE we will periodically post updated images that have the latest system updates
- That's why I recently made some time and threw together a full install guide on how to install stock (up-to-date!!) Armbian yourself. Right now, it runs the miner (even through the internal GPIO pins ), Core, electrs and Core Lightning. The web GUI had some issues building and I don't think I recommend using it, as it requires nodeJS 9.x (very outdated!).
update on my end. i thought i had it figured out. but i woke up this morning and was wrong..... so i reflashed, setup a totally different vlan than it was on, added it on a totally different wifi network instead of the same ether connection it was on before, setup the pool and password on startup, clicked on settings and users and changed the main password to one that is different from default and different than my dashboard login, fired it up, working great, temps around 45 and 62, ran great for 5-8 hours, woke up, changed back to slushpool and topminer01.........(i have tried using multiple pools, keeps reverting back to topminer01 on slushpool) is there something i'm missing? is there a different system password that someone could be accessing to get into it and change everything? i'm at a loss at this point.....
Where did you buy it?
from futurebit. one full node and 3 standard units.
ProfitabilityAs noted earlier, I mostly mined on
https://kano.is/. It's a PPLNS pool, so you only get paid if the pool finds a block and you get rewarded for the last 3 days of shares.
We use PPLNS (Pay Per Last N Shares)
PPLNS means that when a block is found, the block reward is shared among the last N shares that miners sent to the pool, up to when the block was found.
The N value the pool uses is 3 days.
At the time of writing, Kano's last block was #706643; just shy of 236 days ago. Therefore I got no payouts from Kano.
CoinWarz estimates a 3TH/s miner to get roughly 0.00001246BTC per day, so just over 1,000 satoshis. This is roughly the performance I got on NiceHash, as well. It's not much, and therefore I don't think running this device on any level below Turbo (3TH/s) makes any sense. At that point (if you don't care about a somewhat meaningful hashrate), USB stick miners might be more interesting. I own some
Compac F sticks and they can give you a silent operation, less upfront cost and better efficiency than the Apollo hashboard.
Custom LinuxThere's a reason this point is the last one and follows directly the 'profitability' topic. A big selling point for the Apollo BTC (especially in conjunction with the price) is that it's not just a pod miner, but that you get a full node and
can run a 'full Bitcoin stack'.
As mentioned earlier; having this unit mine on kano pool with the stock OS, feels like a bit of a paperweight. No daily payouts, no Electrum server for your SPV wallets and no Lightning. The good news is that it
it can run those things. It's just that there are no OS images or instructions provided by jstefanop.
Ever since I went through the whole manual install process myself (honestly I procrastinated that for a couple months), it instantly became so much more useful. We talked about this in the support thread and assumed that a custom install will require a short USB cable going from the hashboard to the Pi, but I'm pretty glad I got it working through the internal GPIO; so there's no external / visible changes at all.
In case anyone's still looking for it, here's the link to my guide.
https://bitcointalksearch.org/topic/guide-futurebit-apollo-btc-custom-linux-install-base-5401729Unfortunately, I couldn't get openSUSE to run on the Orange Pi, so I resorted to the most reasonable, officially supported OS which was
DebianArmbian.
OS Support:
Android 8.1
Ubuntu 16.04
Ubuntu 18.04
Debian 9
I'm generally quite worried about the security of the stock OS. I honestly see it as just a of proof-of-concept and to check that the hardware works right; other than that it's pretty risky to use it as-is; the Armbian version is outdated, the software packages are outdated and you
have to keep nodeJS 9 on it to have the web UI, which people will inevitably port-forward it to the internet to be able to access it remotely. Just a disaster waiting to happen.
The web GUI, which is admittedly pretty useful, doesn't work without installing outdated nodeJS. I did install it though, and it gave me angry warnings.
I left instructions for installing it in my guide, but opted out of doing so myself. On the miner side, you honestly don't really need more insights than what the pool website tells you, i.e.: 'is my hashrate where it's supposed to be?'. The Bitcoin Core node you can easily check on using
bitcoin-cli getblockchaininfo and for your Lightning Node there's no web GUI provided by Futurebit anyway, so you'll
use Ride-The-Lightning for that.
There's no real conclusion since that's in the TL;DR already, but I again do think it's a potent, little machine, with a tiny size and it can run everything you need at a reasonable noise level. I'd just repeat that it's infinitely more useful once you do install that stuff yourself, onto a fresh, up-to-date, secure Linux distribution. And remember you pay $100 premium on the off-the-shelf parts; so do consider buying those separately and connecting via USB to a 'hashboard-only' Apollo unit.