Official FutureBit Apollo BTC Software/Image and Support thread

[nullama]

~snip~
Regarding the open source interface, please accept my apologies I don't know the github link, could you please be so kind to write it here, once again, for me (and us..) ?

The open source UI consists of these two projects:

UI: https://github.com/jstefanop/apolloui
API: https://github.com/jstefanop/apolloapi

And here are the closed sourced binaries: https://github.com/jstefanop/Apollo-Miner-Binaries

[1714828187]

1714828187

[1714828187]

1714828187

[1714828187]

1714828187

[100knot2dae]

For solo mining directly on your Apollo node, you can install Docker, then build and run a docker image of the solo ckpool using this repository: https://github.com/golden-guy/docker-ckpool

Since I don't have a full node Apollo, I cannot test and verify this myself there unfortunately. But I tested this successfully in similar setups on other SBCs (RPi/Odroid) running Debian/Ubuntu - and the Apollo's OrangePi SBC running Armbian should support the Docker installation as well, as documented here: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-run-docker

Would be great if somebody tried and can give feedback if that has worked out. At least that would be a viable workaround for now for those who feel the itch to solo mine on their Apollo node.

[PakoTor]

For solo mining directly on your Apollo node, you can install Docker, then build and run a docker image of the solo ckpool using this repository: https://github.com/golden-guy/docker-ckpool

Since I don't have a full node Apollo, I cannot test and verify this myself there unfortunately. But I tested this successfully in similar setups on other SBCs (RPi/Odroid) running Debian/Ubuntu - and the Apollo's OrangePi SBC running Armbian should support the Docker installation as well, as documented here: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-run-docker

Would be great if somebody tried and can give feedback if that has worked out. At least that would be a viable workaround for now for those who feel the itch to solo mine on their Apollo node.

ckpool is solving a block more often since I've add my 3 Apollo miner a month ago and it's attracting more miner.s
We went from 26P to 98P.
The only problem is it's not me solving the blocks  with my 14 Th/s

Is there any benefits using the docker as oppose to just entering the pool info?

[jstefanop]

For solo mining directly on your Apollo node, you can install Docker, then build and run a docker image of the solo ckpool using this repository: https://github.com/golden-guy/docker-ckpool

Since I don't have a full node Apollo, I cannot test and verify this myself there unfortunately. But I tested this successfully in similar setups on other SBCs (RPi/Odroid) running Debian/Ubuntu - and the Apollo's OrangePi SBC running Armbian should support the Docker installation as well, as documented here: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-run-docker

Would be great if somebody tried and can give feedback if that has worked out. At least that would be a viable workaround for now for those who feel the itch to solo mine on their Apollo node.

ckpool is solving a block more often since I've add my 3 Apollo miner a month ago and it's attracting more miner.s
We went from 26P to 98P.
The only problem is it's not me solving the blocks  with my 14 Th/s

Is there any benefits using the docker as oppose to just entering the pool info?

Well someone here solve the last ckpool solo block using 10TH worth of Apollos Probably why the pool has attracted more Apollo users since then.

The benefit is that you are using your own node to construct and broadcast the bitcoin block if found, with ckpool, the pool itself has control over the block creation (and therefor could theoretically censor transactions). Until we release our own implimination of solo mining I would not suggest trying to do this on your own unless you know your node is well connected to other pools (which is hard to do on an individual level). We are working with pool partners to directly connect all Apollo solo miners to major pools once our implementation launches.

[kano]

...
Is there any benefits using the docker as oppose to just entering the pool info?

Think of it this way ... if you are using an rpi cpu to do all your bitcoin processing ...

... on top of all the issues with getting that one block you might find out to the world wide bitcoin network fast,
and the fact that your bitcoin needs to see all blocks on the world wide network as fast as possible to reduce the amount of time spent working on stale blocks, ...

how fast do you think an rpi can process that one block you find then send it out,
and how fast do think an rpi can see a new network block, process it and send a work change to your miner?

You would be using an rpi cpu to do all that work ... compared to high performance servers used by pools
(though I will admit your choice of pools is a single server hiding somewhere in the usa with no distribution network of it's own - that loses blocks - so rather an odd choice)

Example: (not sure if the orange pi is up to these specs but ...)
Model: Raspberry Pi 4 Model B Rev 1.5
BogoMIPS: 108.00
Cores/Threads: 4
Features: fp asimd evtstrm crc32 cpuid
Ram: 8GB

.. .competing with ...

One of my nodes (not the higher spec master server)
Model: Intel(R) Xeon(R) E-2286G CPU @ 4.00GHz
BogoMIPS: 7999.96
cpu MHz : 4790.301
Cores/Threads: 12
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
Ram: 32GB

Of course the most useful one there is avx2

... of course my personally modified, performance improved, bitcoin is compiled to use these extra instructions ...

[PakoTor]

... of course my personally modified, performance improved, bitcoin is compiled to use these extra instructions ...

I'm looking at joining your pool but can't see any block found since 2021.
Am I missing something?
I mean how is it better than ckpool if no blocks are found?
The solo's aren't showing?

[100knot2dae]

Is there any benefits using the docker as oppose to just entering the pool info?

You get to learn something new, and - if you are prepared to take the risk - you can save the pool fee if you find a block. Which is up to 2% (as of today, 3300 USD). And in terms of risk, I mainly mean using the Apollo node as mining node from within in your home network. Which has its downsides, as the Apollo node is definitely not as well connected as a pool's mining node, also because your home network will have less uptime stability and lower bandwidth.

[nullama]

~snip~
Well someone here solve the last ckpool solo block using 10TH worth of Apollos Probably why the pool has attracted more Apollo users since then.

The benefit is that you are using your own node to construct and broadcast the bitcoin block if found, with ckpool, the pool itself has control over the block creation (and therefor could theoretically censor transactions). Until we release our own implimination of solo mining I would not suggest trying to do this on your own unless you know your node is well connected to other pools (which is hard to do on an individual level). We are working with pool partners to directly connect all Apollo solo miners to major pools once our implementation launches.

You mentioned in theory ckpool can censor transactions, wouldn't exactly the same statement apply to the "Apollo Pool" since you said the plan is to connect to other servers?

At the end of the day using any pool you need to trust the person behind it.

[jstefanop]

~snip~
Well someone here solve the last ckpool solo block using 10TH worth of Apollos Probably why the pool has attracted more Apollo users since then.

The benefit is that you are using your own node to construct and broadcast the bitcoin block if found, with ckpool, the pool itself has control over the block creation (and therefor could theoretically censor transactions). Until we release our own implimination of solo mining I would not suggest trying to do this on your own unless you know your node is well connected to other pools (which is hard to do on an individual level). We are working with pool partners to directly connect all Apollo solo miners to major pools once our implementation launches.

You mentioned in theory ckpool can censor transactions, wouldn't exactly the same statement apply to the "Apollo Pool" since you said the plan is to connect to other servers?

At the end of the day using any pool you need to trust the person behind it.

By connect to other servers I mean your node will be highly connected to the major mining pool backbone for faster block propagation. You would still be your own "pool" and mining your own blocks/transactions.

FYI cool functionality we are building out is that solo mining will essentially be your own stratum pool (so the pool will run locally on your device and your hashboard will be connected to that internal pool), but the fun part is that you can use it as your own pool infrastructure, so if you have other miners (even non Apollo hardware) you could point all of them to the Apollo and solo mine.

"Pool in a box"

[kano]

~snip~
Well someone here solve the last ckpool solo block using 10TH worth of Apollos Probably why the pool has attracted more Apollo users since then.

The benefit is that you are using your own node to construct and broadcast the bitcoin block if found, with ckpool, the pool itself has control over the block creation (and therefor could theoretically censor transactions). Until we release our own implimination of solo mining I would not suggest trying to do this on your own unless you know your node is well connected to other pools (which is hard to do on an individual level). We are working with pool partners to directly connect all Apollo solo miners to major pools once our implementation launches.

You mentioned in theory ckpool can censor transactions, wouldn't exactly the same statement apply to the "Apollo Pool" since you said the plan is to connect to other servers?

At the end of the day using any pool you need to trust the person behind it.

... and also most important, no one ever has and probably ever will write transaction bias software for your own node.

GBT 'allowed' it, but over the many years GBT existed, no one ever wrote anything to do it,
not even Luke who used to spout this as a reason to use GBT.

[nullama]

~snip~
By connect to other servers I mean your node will be highly connected to the major mining pool backbone for faster block propagation. You would still be your own "pool" and mining your own blocks/transactions.

FYI cool functionality we are building out is that solo mining will essentially be your own stratum pool (so the pool will run locally on your device and your hashboard will be connected to that internal pool), but the fun part is that you can use it as your own pool infrastructure, so if you have other miners (even non Apollo hardware) you could point all of them to the Apollo and solo mine.

"Pool in a box"

That sounds promising.

I hope it ends up being published as open source. I bought the Apollo assuming it to have open source software for the mining(like cgminer for example), but was disappointed to realize it only has a closed source binary available to mine with. By the way, I remember you mentioned some time ago that the code could be open if the Apollos did well financially, and I think they have done well based on this thread and they being sold out all the time. Are we getting an open source miner for the Apollos?

[initforthelearning]

Is there one? If so, what is it? I've reached out through multiple direct channels for help with a failed unit < 90 days old and have received no response (yet). Is this typical post sales support?

[100knot2dae]

Is there one? If so, what is it? I've reached out through multiple direct channels for help with a failed unit < 90 days old and have received no response (yet). Is this typical post sales support?

If it's a warranty case, check back with your reseller first. He should be able to directly sort that out with you or file a support case on Futurebit side.

[initforthelearning]

Is there one? If so, what is it? I've reached out through multiple direct channels for help with a failed unit < 90 days old and have received no response (yet). Is this typical post sales support?

If it's a warranty case, check back with your reseller first. He should be able to directly sort that out with you or file a support case on Futurebit side.

I bought direct from futurebit and have tried all the usual support channels (chat, email, replying to my order email etc) over the past week but no response. Wondering is that was to be expected or an anamoly?

[initforthelearning]

The other thing I'm trying to figure out if if there is an alternate power adapter people here have found that works reliably with Apollo? I think that's the source of the issue I'm having and if I don't get support for a warranty replacement I doubt I'd buy another one from Futurebit. I understand it's possible to run 300 W+ adapters with Future Bit and the checking I've done seems to indicate that it's possible to find one that runs quite a bit cooler (say 40 C instead of 60 C) than the one that FutureBit offers, but so far I haven't found one with dual 6 pin connectors. Any suggestions?

[100knot2dae]

Is there one? If so, what is it? I've reached out through multiple direct channels for help with a failed unit < 90 days old and have received no response (yet). Is this typical post sales support?

If it's a warranty case, check back with your reseller first. He should be able to directly sort that out with you or file a support case on Futurebit side.

I bought direct from futurebit and have tried all the usual support channels (chat, email, replying to my order email etc) over the past week but no response. Wondering is that was to be expected or an anamoly?

I don't have experience with their direct support, but I doubt this is normal. Maybe raise the issue here and quote @jstefanop for support. In regards to power supply: You can actually use any good power PC supply, you just need to bridge two pins on the ATX plug to make it jump-start.
If you need to buy one, I would recommend the most efficient one you can afford. Because this will likely run 24/7, so 80 Plus Gold or better.

[jstefanop]

Is there one? If so, what is it? I've reached out through multiple direct channels for help with a failed unit < 90 days old and have received no response (yet). Is this typical post sales support?

If it's a warranty case, check back with your reseller first. He should be able to directly sort that out with you or file a support case on Futurebit side.

I bought direct from futurebit and have tried all the usual support channels (chat, email, replying to my order email etc) over the past week but no response. Wondering is that was to be expected or an anamoly?

We respond to all support emails and as far as I can see we dont have any open tickets right now so maybe your email is not going through? FYI all Apollos comes with a standard one year warranty.

[initforthelearning]

Is there one? If so, what is it? I've reached out through multiple direct channels for help with a failed unit < 90 days old and have received no response (yet). Is this typical post sales support?

If it's a warranty case, check back with your reseller first. He should be able to directly sort that out with you or file a support case on Futurebit side.

I bought direct from futurebit and have tried all the usual support channels (chat, email, replying to my order email etc) over the past week but no response. Wondering is that was to be expected or an anamoly?

We respond to all support emails and as far as I can see we dont have any open tickets right now so maybe your email is not going through? FYI all Apollos comes with a standard one year warranty.

Hi. I got a response on Monday to the email I sent that was a reply to my order. I followed the suggestion in that email to do a power cycling of the standard and reboot the main unit. Both units fired up as normal and I thought that resolved the issue. However I noticed a few anomalies after that. At first I wasn't sure if these anomalies were actual problems and so I started to compose an email to you yesterday regarding what I was noticing.  However, then I noticed the connectors to the full unit were hot to touch (on balanced mode, with no node syncing) and upon closer inspection I saw that those connectors had burned out. That appears to be a new issue. I hadn't noticed any problems with the full unit before; I just thought their might be an issue with the power supply to the standard. In any case, I sent you pictures yesterday (reply to the order email thread). Both units are now off, out of commission, for safety, awaiting your response. Thanks.

[thebtctotoro]

Apollo BTC Standard Software/Instructions


If your purchased an Apollo BTC Standard USB controlled version please find the software binaries for your system and instructions below:

https://github.com/jstefanop/Apollo-Miner-Binaries/releases/

This is the ONLY place you should download these binaries from. If that changes this post will be updated.

Detailed instructions are on the GitHub and inside the start scripts. As noted in the pre-order this is command-line based software and only intended for more advanced users. Support for the software is limited and initial binaries are for Windows and 64 Bit x86 and ARM based Linux systems.


This software is only for users that do not have a Full Package/Node version. Please follow the instructions above in the first post on how to hook up your standard unit to your Apollo Full Package unit for a plug and play experience.

Hello,
I wanted to throw out a suggestion.  I am a big fan of the standard units, i love running them on basically whatever machine I have lying around...they are very flexible in that way.  I am also a big fan of Start 9's embassy OS.  I wanted to suggest creating a service on embassy OS that would work in their operating system to click and run any standard units one could have plugged into the computer running embassy OS.  Embassy OS has a suite of applications meant to be run for self-hosting various services (such as bitcoin core, lightning node, but also other things like jellyfin and nextcloud...really anything that a user would want running on a computer 24/7).  So, since that computer with embassy OS will be running 24/7, if I could plug my standard units into my machine running embassy, and open a service in that OS to fire up the miners, point them to the right pool, etc...I think that would be pretty amazing.  Also - I think it could really benefit the futurebit apollo project as there may be many users of embassy OS that would love to buy a futurebit standard miner and try it out with their embassy OS upon release of this cool new service

Anyways, here is their github link: https://github.com/Start9Labs/embassy-os/releases.  They have a pretty active community marketplace, where developers of other projects can create services in the embassy OS ecosystem.  Thanks for your consideration, hopefully this finds the right eyeballs for review. 

[initforthelearning]

I'm just reporting back that I appreciate the personal help from FutureBit that has transpired between my last post here and today. I've sent back the full Apollo to replace the connectors and PSU. Once it is been returned to me, I will have a full and a standard that should be in good shape. I've read some previous posts sometimes someone is interested in additional units. I would be open to considering selling mine to any interested parties.