Hello Team, for solo mining on the Apollo 2, is it possible to manipulate any mining inputs like inscribing into the coinbase (ex “Chancellor on brink….” or maybe the extraNonce or anything else to customize and further randomize the hashes?
Thats on our to do list and will add that as an option for a future update (customizing solo coinbase tag). Ok thanks. What’s the current default coinbase tag if I’m lucky to mine a block? And to confirm, there is no other way to customize the mining algorithm (besides having a unique wallet address)? It's something like "Mined by a Solo FutureBit Apollo"...no these are ASICs, algo is hardcoded in the hardware itself there is no way to change the mining algorithm like a GPU. |
|
|
|
thanks, I figured it out now and setup custom pool.
I am going to open up the case and see if there is any chance to figure out how to water cool these using a computer 360 AIO.
the device is fantastic BUT ... even in ECO mode and fan at 2200rpm its LOUD to sit on your desk in office or bedroom. on Balanced mode and fan at 3300rpm its VERY loud and unless you you have a house and can keep it in garage away from you, its just not practical to have in an apartment. The Turbo mode is ridiculously loud, like a jet taking off.
frankly even in Balanced mode, I dont see the longevity of the fan spinning at such high RPMs for months and years and the amount of dust it will collect with so much air being sucked in will require regular maintenance / cleaning as it will otherwise overheat.
its a great device but the cooling just doesnt work above ECO mode and needs watercooling solution.
the device cost me $2000 Australian dollars after shipping and taxes. A 360 AIO costs $100 so Im surprised they have not offered it as an option with an external box attached to the Apollo II with the fan and radiator. I would be very happy with that as who cares about aesthetics.
We already have a custom water block and radiator solution, I didn't like how loud the device was as well in balance/turbo but 90% of customer feedback from the Apollo BTC was maximum utilization of the ASICs which meant higher noise levels in balance/turbo. Was worth it for us since almost everyone runs the devices in eco so noise levels were comparable there, and the 10% that want max performance run them in garages etc where slightly higher noise does not matter. Waterblock we have is crazy overkill, we are talking about 500+ watts at under 2k RPM speeds. Cost alone of the water block/radiator is over 200 so adding that much more to the cost was not worth it. Next gen asics might get interesting since those can burn up to 20 watts each which requires either crazy high fan speeds or some kind of water/immersion solution. If we can 2-3x hashrate again and keep prices close to where they are water block might make sense. |
|
|
|
FWIW this bug only affected the best difficulty being stored to the non-volatile memory. Nothing to do with shares yea amount of 32 bit buffer overrun bugs in our new UI was fun tracking down... btw hope you guys have simulated a very high share in your firmware...early miner firmware was notorious for bugs like this but in the actual shares, so the miner would crash/submit an invalid share for an actual block find... |
|
|
|
So I ordered a standard Apollo II and this is my 6 unit from Futurebit. ( moonlanders, Apollo LTC, Apollo Btc) some fries from the 6 pins connectors later.. and my full node first batch just stopped hashing 3 months ago .. still don’t know why …. HERE you have a cool hack : I converted a standard Apollo II into a full node version with the first MCU ! Working by Wifi Porn pics here :  haha awesome... I personally left the 5v pin on the new board connected (new controllers take 5v directly from DCDC board now), just so it could be backwards compatible with the old controllers  Glad its working for you! |
|
|
|
how do we check the power usage of the standard unit if we are running it via a raspberry pi or different computer? not sure how to read the terminal/command line results haha.
i got mine running yesterday, just wanted to confirm i was able to run the binaries for the Apollo II standard unit. i got it working on a $40 thinkpad 11e [it was a chromebook but i installed linux mint on it] so it should work on most setups.
Awesome good to know! Power usage is on the top where is says "BOARD SYS INFO" the last value on the line is the power usage (under P, wt) |
|
|
|
Hello Team, for solo mining on the Apollo 2, is it possible to manipulate any mining inputs like inscribing into the coinbase (ex “Chancellor on brink….” or maybe the extraNonce or anything else to customize and further randomize the hashes?
Thats on our to do list and will add that as an option for a future update (customizing solo coinbase tag). |
|
|
|
Hello,
I´ve start the Apollo II for first time and created the WEB password (with a german keyboard).
Now I can´t login tu the Website of my Apollo II.
ssh as root (futurebit123 worked well), changed password for user futurebit worked also well, but the WEB-password must be independed of system password.
How can I change the Apollo II WEB-password?
Hi did you use German characters for the password? Can you DM me an example so we can test if this is causing issues. The futurebit user password (for OS login screen) is set to the web UI password you set during the web setup. Usually you need to reflash your SD card if you cant login, but since you seem to know your way around ssh you can just delete the .sqlite database file in /opt/apolloapi and it will force setup again. |
|
|
|
Hello FutureBit!
I received my apollo-2 full node systems about a month ago,
and it's been quite an educational journey! I joined the
ocean pool and received my first payout with lightning.
However a few days ago the bitcoin nodes on both my apollo-2
systems (configured as TOR mode) lost connection to other nodes,
so they're stuck syncing blocks (~644000/844366).
Tor logs in /var/log/syslog are filled with messages like this :
May 22 04:49:35 futurebit-apollo-2 Tor[202872]: No circuits are opened. Relaxed timeout for circuit 123467 (a Hidden service client: Fetching HS descriptor 4-hop circuit in state waiting to see how other guards perform with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1348 similar message(s) suppressed in last 3900 seconds]
May 22 09:42:24 futurebit-apollo-2 Tor[202872]: We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [4454 similar message(s) suppressed in last 600 seconds]
May 22 09:47:18 futurebit-apollo-2 Tor[202872]: Failed to find node for hop #1 of our path. Discarding this circuit.
The internet connection is fine, and the miner continues to contribute
to the ocean pool.
I am able to use tor from other computers on my LAN.
Rebooting the apollo-2 does not help.
Tor version 0.4.6.10 is a couple years old.
How are updates managed?
Do you have any hints about this?
Thanks!
Tor is notorious for sync issues. I would temporarily turn tor off and let the node sync then turn it back on. Update issues have been resolved, so as long as you dont do a dist upgrade you should be fine with apt update/upgrade going forward (kernel is now frozen). |
|
|
|
Can you send output of ./apollo-miner-v2 --help (top line version/build date).
Sure thing: $ ./apollo-miner-v2 --help
apollo-miner 2.0.2-c 2024-03-20, msp ver 0xd166
Ahh oops uploaded the Apollo 1/BTC binary will fix shortly. |
|
|
|
|
FYI If you have been trying to solo mine with a taproot address and stuck on "Waiting for Share" the issue is the taproot address.
Only legacy or Segwit addresses are supported for Solo mining currently
EDIT: Actually its all 62 char addresses so P2WSH (pay to witness script hash) and P2TR (pay to taproot) wont work either.
Just legacy, script, and normal SegWit (P2WPKH) are supported.
|
|
|
|
Good morning. Perhaps covered elsewhere but could not readily find a resolution.
Got my Apollo II plugged in a few days ago and sync'ed to the current block but mining function is getting error message of [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4445094100
Any insight as to how to resolve?
Thank you.
Updated to 2.0.4 if you have not already done so. There is also another overflow bug that is fixed in 2.0.5 (out in the next few days) but a reboot will fix this temporarily. FYI this is just a UI bug (everything in the backend miner/node is still working fine). Thank you, updating to 2.0.5 resolved this issue. One question, the unit seems to beep intermittently for different length of time, no real pattern to it. Is there a way to turn that beeping off? We havent released 2.0.5 yet. Beep? There is no speaker on the Apollo, I believe there is a beeper on the board, but this is not used. |
|
|
|
Running the new binaries for my Apollo 2 Standard on a Raspberry Pi 4 after updating the start_apollo.sh script, it looks like apollo-miner-v2 is not detecting my miner. *** MASTER STATS:
Date: 2024-05-18 18:50:55, UpTime: 241 secs, mbHwVer: 0x0, osc: 0
Smooth osc: step: 1, ignore broken pwc: 0
Found boards: 0
Broken SPI: 0
Then it scrolls off the screen repeating this: MsPacket: version mismatch: act 0xd167 != exp 0xd166
WARNING: slave[0]: packet ignored
And the status update shows this: *** MASTER-SLAVE SPI BUS STATS:
SLAVE UID B-LEN B-CRC-C B-CRC-L VER TIME PING M=>S rx err % S=>M rx err % SS SD Rst LastRstT Packets Time msec. Speed(pack./sec)
0 000000000000000000000000 0 00000000 00000000 0x00000000 0 666666 3121 0 3118 100.0% 0 0 0 0.0% 0 0 0 0
Any ideas? Can you send output of ./apollo-miner-v2 --help (top line version/build date). |
|
|
|
Good morning. Perhaps covered elsewhere but could not readily find a resolution.
Got my Apollo II plugged in a few days ago and sync'ed to the current block but mining function is getting error message of [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4445094100
Any insight as to how to resolve?
Thank you.
Updated to 2.0.4 if you have not already done so. There is also another overflow bug that is fixed in 2.0.5 (out in the next few days) but a reboot will fix this temporarily. FYI this is just a UI bug (everything in the backend miner/node is still working fine). |
|
|
|
Support for Apollo II USB Standard units on your own linux/windows systems has been released below: https://github.com/jstefanop/Apollo-Miner-BinariesRelease section has not been updated yet so click on "Code" then download Zip and run the appropriate binary for your system. Will also upload updated Apollo 1/BTC binaries next week. Sorry this took so long windows port took longer than expected...had to compile under GCC for windows (not msvc) so has only been tested under windows 10 as working. Let me know if anyone has any .dll errors. |
|
|
|
I read in other apollo1 topic that a software update is waithing. I cant belive it, I buy Apollo2 standard unit which I cant use it because I dont own Apollo1.  Standalone binary support for Apollo II has been released here: https://github.com/jstefanop/Apollo-Miner-BinariesRelease section has not been updated yet so click on "Code" then download Zip and run the appropriate binary for your system. |
|
|
|
And all of us are lucky that Avalon / Canaan is shipping slowly if they were fast it would kill off all of the units above.
That’s a good point! You have to wonder why they are half-assing the sales. Is production just not ready yet? Is this a temporary, loss-leader product? Maybe a limited supply of chips? I guess we’ll find out. Margins have got to be razor thin with 10 chips in there. I can assure you that none of the projects you listed are getting “killed off”. More like “super motivated” now. They are using their garbage ASICs (literally ASICs they would throw away) to make these. This is why they can charge 150 for them, even the parts probably costs more than 150 from some teardown ive seen. This is not a sustainable volume product thats why they are not making a lot. |
|
|
|
Temperatures:
What are the safe temps for the miner? I was 67C for Eco mode, now I'm at 71 - 73 for Balanced mode. Before I try out turbo mode, I'd like to know at what temperature I need to throttle it back?
Anything under 80c is fine for these ASICs, the miner has mutiple levels of protection and will auto shut down power at 83+ (even if the fan or controller dies) The fan/temps are tuned for quiet operation...if you are running these in a garage or basement you can set a manual fan profile that keeps temps even cooler for slightly better efficiencies |
|
|
|
What's shipping looking like for April orders?
Currently shipping march orders, should have those done by end of the month. April orders should start going out early June. Leadtimes will probably decrease end of the month as we catch up to demand. |
|
|
|
~snip~
Yes sorry for the delay on this was supposed to have these out by now but ran into some issues with windows binaries..will at the very least release the linux binaries on Monday.
Are the binaries for Apollo I being updated as well or is that project abandoned? It's been a few years since the last update. December 2021: https://github.com/jstefanop/Apollo-Miner-Binaries/releasesNope completely updated codebases for both Apollo I and Apollo II being released hopefully by tomorrow. |
|
|
|
Is anybody able to connect Sparrow to the node with the new UI? Did you change anything in the bitcoin.conf file? Not able to connect... (User is "futurebit", right?)
Next point release has a one button "Enable wallet connections to my node" with instructions to make this dumb proof. Editing the bitcoin.conf file in UX was still not easy enough so hopefully this takes care of most use cases. |
|
|
|
|
Show Posts
