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

[PegasusNZ]

Hello, we already tried that image that you highlighted in this last message, but it is the same one that we tried the first time. The 1.93 GB MCU2 version. And it does the same...

 And the version of etcher is v1.18.11
The same one that happened to us
 The failure is very rare... and after several tests it remains the same...

Try a different monitor or find the IP address of your unit and SSH into it to see what is going on

[jstefanop]

Hello!

Will FutureBit consider supporting the emerging DATUM protocol soon?
I wish my FutureBit Apollo II Full Node BTC Miner to use DATUM.

https://ocean.xyz/docs/datum

If there is wide support yes, wasted my time with stratumv2 with no pool support so not going down that route again.


Not sure why you would want this over what the Apollo II already provides, which is a self hosted solo pool to your own node, its 10x more decentralized than what datum wants to do (which at the end of the day is another stratumv2 implementation with the same central control and custodian issues).

[PennyBit]

Hi jstefanop,

Haven't heard from anybody on this question, can you help?

In the first image below, I don't understand why my stat values jump to these laughable odd placement values when I have two Apollo II standard units connected to my Apollo II full node unit. It doesn't occur with a single unit connected to the Apollo II full node unit, only when I have two connected.

https://ibb.co/7kyQGKH

In this second image below, I simply don't know what the "36.97A" is referring to. I have to assume there's no way it's referring to amps. Anyone know?

https://ibb.co/FVty8p1

I'm on v2.0.5.

Thanks for any help.

Cheers!

[jstefanop]

Hi jstefanop,

Haven't heard from anybody on this question, can you help?

In the first image below, I don't understand why my stat values jump to these laughable odd placement values when I have two Apollo II standard units connected to my Apollo II full node unit. It doesn't occur with a single unit connected to the Apollo II full node unit, only when I have two connected.

https://ibb.co/7kyQGKH

In this second image below, I simply don't know what the "36.97A" is referring to. I have to assume there's no way it's referring to amps. Anyone know?

https://ibb.co/FVty8p1

I'm on v2.0.5.

Thanks for any help.

Cheers!

Overview screen shows averages when mutiple units are connected. Need to fix that formatting error and rethink this.

It is indeed the board current, it's how we get total watts the miner is using.

[MakerAZ]

Hello!

Will FutureBit consider supporting the emerging DATUM protocol soon?
I wish my FutureBit Apollo II Full Node BTC Miner to use DATUM.

https://ocean.xyz/docs/datum

If there is wide support yes, wasted my time with stratumv2 with no pool support so not going down that route again.


Not sure why you would want this over what the Apollo II already provides, which is a self hosted solo pool to your own node, its 10x more decentralized than what datum wants to do (which at the end of the day is another stratumv2 implementation with the same central control and custodian issues).

As OCEAN's explains Stratumv2 did not allow to accomplish what they wanted.
I am NOT solo mining, so when I mine with OCEAN am I currently the one to build my one block template? I don't think so. 10x more decentralized in what sence? To my understanding OCEAN's concern is centralization of building block tempaltes. Can I configure my FutureBit Apollo II Full Node BTC Miner to build block templates rejecting ordinals while still mining in a pool?

[LeoFist]

Hi jstefanop,

Re "screen -dr node", you mentioned that "as long as you see getblocktemplate messages your solo mining".

I don't see any GetBlockTemplate messages but I do see continuous CreateNewBlock() messages. Is that what you meant? Just want to confirm please.

Thanks!

[jstefanop]

Hi jstefanop,

Re "screen -dr node", you mentioned that "as long as you see getblocktemplate messages your solo mining".

I don't see any GetBlockTemplate messages but I do see continuous CreateNewBlock() messages. Is that what you meant? Just want to confirm please.

Thanks!

yea thats right.

[jstefanop]

Hello!

Will FutureBit consider supporting the emerging DATUM protocol soon?
I wish my FutureBit Apollo II Full Node BTC Miner to use DATUM.

https://ocean.xyz/docs/datum

If there is wide support yes, wasted my time with stratumv2 with no pool support so not going down that route again.


Not sure why you would want this over what the Apollo II already provides, which is a self hosted solo pool to your own node, its 10x more decentralized than what datum wants to do (which at the end of the day is another stratumv2 implementation with the same central control and custodian issues).

As OCEAN's explains Stratumv2 did not allow to accomplish what they wanted.
I am NOT solo mining, so when I mine with OCEAN am I currently the one to build my one block template? I don't think so. 10x more decentralized in what sence? To my understanding OCEAN's concern is centralization of building block tempaltes. Can I configure my FutureBit Apollo II Full Node BTC Miner to build block templates rejecting ordinals while still mining in a pool?

Central Pools are the main centralization issue with bitcoin mining right now. The Apollo BTC/II circumvents this entirely by running your own "pool". You cant get anymore decentralized in mining than this.

It's great what ocean is doing, but they are still a central entity in the mining peg and can easily be controlled/shutdown etc.

[rayday11]

There is a max connections setting, on the node. What would be the recommendations for setting this?

[PegasusNZ]

There is a max connections setting, on the node. What would be the recommendations for setting this?

I think the default is 30 which is a nice number

[Sledge0001]

There is a max connections setting, on the node. What would be the recommendations for setting this?

I have mine set at 50 and it doesn't impact CPU or network performance at all.

[AQUARIUZ88]

hello all sos plz!

can anyone have be some guidance currently running the apollo II solo mining on v2.0.5 I am getting this ( [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2179756302 ) flickering on/off the node is on but the solo mine stays off as i intend to turn it on.

[PegasusNZ]

hello all sos plz!

can anyone have be some guidance currently running the apollo II solo mining on v2.0.5 I am getting this ( [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2179756302 ) flickering on/off the node is on but the solo mine stays off as i intend to turn it on.

[GraphQL error] is a known bug and will be fixed in the next release which is due very soon! It is a GUI bug and does not effect the operation of the Apollo

[CryptoCellLabs]

I have a FullNode version of Apollo BTC1 (the latest Apollo OS 2.0.5), which suddenly broke recently. The specific symptoms are as follows:
1. The front panel flashes quickly and then stays on after powering on.
2. Unable to find IP on router
3. The display does not light up either

I tried connecting it to another normal FullNode machine, but the host doesn't recognize this machine either (using a microUSB connection)

I can't find this FullNode machine under macos and windows, use microUSB to connect

The other three FullNode Apollo BTC1 machines were normal, but the broken machine also broke suddenly without any warning.

[quickmr2]

Is there a way to turn off the mining aspect on an original Apollo btc miner and just use it as a node?

[Joelnolan]

I've been renting hash power and trying to send to my solo pool but it doesnt work because the difficulty is too low. Is there anyway to increase that or is it not worth it?

[PegasusNZ]

Is there a way to turn off the mining aspect on an original Apollo btc miner and just use it as a node?

Yes, you can stop the miner in the GUI and the node will continue to run
GUI options:
  1 on the miner screen at the top hit stop miner
  2 hit the power button top right and select stop miner

SSH options:
  1 sudo systemctl stop apollo-miner.service
  2 If you want to make it permanent after stopping the service sudo systemctl disable apollo-miner.service

[AQUARIUZ88]

hello all sos plz!

can anyone have be some guidance currently running the apollo II solo mining on v2.0.5 I am getting this ( [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2179756302 ) flickering on/off the node is on but the solo mine stays off as i intend to turn it on.

[GraphQL error] is a known bug and will be fixed in the next release which is due very soon! It is a GUI bug and does not effect the operation of the Apollo

thank you thank you very much I am trying to learn the ropes much is appreciated.

[NotFuzzyWarm]

I've been renting hash power and trying to send to my solo pool but it doesnt work because the difficulty is too low. Is there anyway to increase that or is it not worth it?

A. Renting hash to point at your node is a bad idea. Throwing $$ at your private node is insane... Do you have redundant infra and connections to the 'net to broadcast Block Found info to the multiple sites around the world that well run pools use? Odds are - no. I would NEVER risk losing a block in an orphan race against better connected pools like that...

 B. Most hash rentals require an initial connection minimum diff of 1,000,000 to run due to the size of the 'mega-miner' they are providing.

[Joelnolan]

I've been renting hash power and trying to send to my solo pool but it doesnt work because the difficulty is too low. Is there anyway to increase that or is it not worth it?

A. Renting hash to point at your node is a bad idea. Throwing $$ at your private node is insane... Do you have redundant infra and connections to the 'net to broadcast Block Found info to the multiple sites around the world that well run pools use? Odds are - no. I would NEVER risk losing a block in an orphan race against better connected pools like that...

 B. Most hash rentals require an initial connection minimum diff of 1,000,000 to run due to the size of the 'mega-miner' they are providing.

Noted. thanks for the info