Official FutureBit Apollo BTC Software/Image and Support thread - page 23.

magicpete

newbie

Activity: 1

Merit: 0

I'm curious if anyone has figured out a way to schedule their Apollo 2 to change modes based on time of day. Would be helpful to switch off during peak hours and step up to turbo overnight. I know it's not in the OS but my next step was to explore scripting something to do this.

philipma1957

legendary

Activity: 4326

Merit: 8950

'The right to privacy matters'

Quote from: MakerAZ on July 30, 2024, 09:43:06 PM

Quote from: jstefanop on July 30, 2024, 01:21:59 PM

Not sure what your asking, once a valid block is found it submitted to your local node within a couple hundred milliseconds and then your node broadcasts to the entire network (limited by your upload speed, but should still be less than a few seconds even in low end connections).

There wont be "hundreds of blocks" in between, there is a block every 10 minutes on average.

Let me try to explain that again.

I want to give my personal miner "unlimited" amount of time to mine a valid block, as if there are no other miners in the network, but me alone.
Even if it could take days for my miner to finally find a block, I want it to continue mining on that same block.

This means, that my node should be "offline" and remain "offline" from the entire network, so no new blocks are reported to it, but remain "online" within my home network so my miner can continue mining the SAME block header.

I do understand that by the time my miner finds a valid block, the entire network will be mining a block way higher and my valid block will not be accepted as most probably it will take days to find it.

I hope it is clear now.

First of all if you are mining with 100th and the current difficulty number of 90.6 t it will take over 1000 years to hit the block.

100 th would mine 0.000007 btc a day since a block is 3.25 btc divide by 0.000007 and get 464285 days or 1272 years to hit a block.

They is simply no reason to do what you are trying to do.

and if I am correct and you gear is more like 6th take that 1272 years and go 15x or 19080 years. Why would you want to do what you want to do?

crypto_curious

full member

Activity: 933

Merit: 175

Device: Apollo II standard USB unit, first batch

Problem: device never stops mining (I can feel the heat coming out of the vent and fan is spinning quite loud), even when pool is down, or mining software apollo-miner-v2 executable is not running on connected (via USB) computer

Apollo I did not have this problem, and I can disable mining program and device will cool down quickly. I use it with a script and thermometer to turn on and off Apollo I when needed.
Apollo II never stops burning electricity for nothing, even when it supposed to be idle, I can't temperature-control it, it's just working non-stop.

Please tell me how can I tell it to stop burning electricity for nothing?

I am using latest available binary on Linux AMD64:

Code:

./apollo-miner-v2 --version
apollo-miner 2.0.2 2024-05-18, msp ver 0xd167
Use "--help" switch to print command line options.

ERROR: Invalid command line:
Unknown command line option: --version

MakerAZ

newbie

Activity: 27

Merit: 5

Quote from: jstefanop on July 30, 2024, 01:21:59 PM

Not sure what your asking, once a valid block is found it submitted to your local node within a couple hundred milliseconds and then your node broadcasts to the entire network (limited by your upload speed, but should still be less than a few seconds even in low end connections).

There wont be "hundreds of blocks" in between, there is a block every 10 minutes on average.

Let me try to explain that again.

I want to give my personal miner "unlimited" amount of time to mine a valid block, as if there are no other miners in the network, but me alone.
Even if it could take days for my miner to finally find a block, I want it to continue mining on that same block.

This means, that my node should be "offline" and remain "offline" from the entire network, so no new blocks are reported to it, but remain "online" within my home network so my miner can continue mining the SAME block header.

I do understand that by the time my miner finds a valid block, the entire network will be mining a block way higher and my valid block will not be accepted as most probably it will take days to find it.

I hope it is clear now.

jstefanop

legendary

Activity: 2174

Merit: 1401

Quote from: MakerAZ on July 29, 2024, 03:44:44 AM

Dear Support,

I want to ensure that my Solo mining configured correctly and really works.

How can I Solo mine to my local Full Node without being interrupted by newly mined blocks.

I mean I want to let Apollo II to take as much time as needed to find a valid block. I do understand that by the time the valid block is found there will be hundreds of new blocks and my block will not be accepted. How can I achive this?

Not sure what your asking, once a valid block is found it submitted to your local node within a couple hundred milliseconds and then your node broadcasts to the entire network (limited by your upload speed, but should still be less than a few seconds even in low end connections).

There wont be "hundreds of blocks" in between, there is a block every 10 minutes on average.

MakerAZ

newbie

Activity: 27

Merit: 5

Dear Support,

I want to ensure that my Solo mining configured correctly and really works.

How can I Solo mine to my local Full Node without being interrupted by newly mined blocks.

I mean I want to let Apollo II to take as much time as needed to find a valid block. I do understand that by the time the valid block is found there will be hundreds of new blocks and my block will not be accepted. How can I achive this?

jstefanop

legendary

Activity: 2174

Merit: 1401

Quote from: eekbert on July 28, 2024, 07:13:30 AM

Hi, I recently received my Apollo II full node. I am mining solo. I noticed that the starting difficulty is very low, and increases very slowly. Also, seems the maximum difficulty does not go very high. Is there a way to set the mining difficulty or at least the starting difficulty? Thanks.

on the to-do list!

jstefanop

legendary

Activity: 2174

Merit: 1401

Quote from: bluudz on July 25, 2024, 05:14:50 PM

Quote from: bluudz on July 25, 2024, 03:22:56 PM

Quote from: TIRMINE on July 25, 2024, 09:22:36 AM

Quote from: bluudz on July 25, 2024, 02:34:44 AM

Hey everyone.
Very happy with my Apollo 2 so far. Only thing I'm a bit struggling with is to get node to connect to more peers. Any workaround? I did add quite a few through addnode=x.x.x.x:8333 but still it doesn't seem to connect easily to more than 10 peers.

Any ideas how to get more peers to connect to the node?

Also I was wondering whether there shouldn't be field or some way to show when one finds block! Otherwise it could take long time before you realize you actually found one.

Thanks

Are you fully synced? When I was syncing it would max at 10 for me but once fully synced I'm getting the 32

Yes. Fully synced and solo mining. Max connections set to 40, but only connected to 11.

Edit: Got this resolved. Last night when I added nodes I also changed max connections and now when I looks to bitcoin.conf in the node it didn't actually addnodes at all, even tho it was showing in the gui Ui so I have added them manually and now I have 20 connections at least.

Unfortunately it seems there is some kind of bug with my configuration. Every time I restart the miner it takes first addnode=x.x.x.x and populate with same ip address all other entries in my bitcoin.conf. When I manually change bitcoin.conf and only restart node it does work fine and connects to all ips, but as soon as whole miner get restarted it does again wipe all ips in .conf except the first one. Not really sure what is causing this.

This is a known issue with some custom node configs that will also be fixed in 2.0.6

eekbert

newbie

Activity: 6

Merit: 0

Hi, I recently received my Apollo II full node. I am mining solo. I noticed that the starting difficulty is very low, and increases very slowly. Also, seems the maximum difficulty does not go very high. Is there a way to set the mining difficulty or at least the starting difficulty? Thanks.

TIRMINE

jr. member

Activity: 123

Merit: 4

This has been fixed on dev, finally got to the source of all the 32bit errors. Should push 2.0.6 soon.
[/quote]

Any update on 2.0.6? I'm now getting this error too

johnstewart

jr. member

Activity: 31

Merit: 4

Hello Everyones !

Can you please tell me exactly wich model of MCU is in the Apollo 2 ? it seems it's an orange pi 4 but i'm not shure if it's this one ?

Thanks you !!!! Wink

bluudz

full member

Activity: 215

Merit: 116

Why so serious?

Quote from: bluudz on July 25, 2024, 03:22:56 PM

Quote from: TIRMINE on July 25, 2024, 09:22:36 AM

Quote from: bluudz on July 25, 2024, 02:34:44 AM

Hey everyone.
Very happy with my Apollo 2 so far. Only thing I'm a bit struggling with is to get node to connect to more peers. Any workaround? I did add quite a few through addnode=x.x.x.x:8333 but still it doesn't seem to connect easily to more than 10 peers.

Any ideas how to get more peers to connect to the node?

Also I was wondering whether there shouldn't be field or some way to show when one finds block! Otherwise it could take long time before you realize you actually found one.

Thanks

Are you fully synced? When I was syncing it would max at 10 for me but once fully synced I'm getting the 32

Yes. Fully synced and solo mining. Max connections set to 40, but only connected to 11.

Edit: Got this resolved. Last night when I added nodes I also changed max connections and now when I looks to bitcoin.conf in the node it didn't actually addnodes at all, even tho it was showing in the gui Ui so I have added them manually and now I have 20 connections at least.

Unfortunately it seems there is some kind of bug with my configuration. Every time I restart the miner it takes first addnode=x.x.x.x and populate with same ip address all other entries in my bitcoin.conf. When I manually change bitcoin.conf and only restart node it does work fine and connects to all ips, but as soon as whole miner get restarted it does again wipe all ips in .conf except the first one. Not really sure what is causing this.

bluudz

full member

Activity: 215

Merit: 116

Why so serious?

Quote from: TIRMINE on July 25, 2024, 09:22:36 AM

Quote from: bluudz on July 25, 2024, 02:34:44 AM

Hey everyone.
Very happy with my Apollo 2 so far. Only thing I'm a bit struggling with is to get node to connect to more peers. Any workaround? I did add quite a few through addnode=x.x.x.x:8333 but still it doesn't seem to connect easily to more than 10 peers.

Any ideas how to get more peers to connect to the node?

Also I was wondering whether there shouldn't be field or some way to show when one finds block! Otherwise it could take long time before you realize you actually found one.

Thanks

Are you fully synced? When I was syncing it would max at 10 for me but once fully synced I'm getting the 32

Yes. Fully synced and solo mining. Max connections set to 40, but only connected to 11.

Edit: Got this resolved. Last night when I added nodes I also changed max connections and now when I looks to bitcoin.conf in the node it didn't actually addnodes at all, even tho it was showing in the gui Ui so I have added them manually and now I have 20 connections at least.

TIRMINE

jr. member

Activity: 123

Merit: 4

Quote from: bluudz on July 25, 2024, 02:34:44 AM

Hey everyone.
Very happy with my Apollo 2 so far. Only thing I'm a bit struggling with is to get node to connect to more peers. Any workaround? I did add quite a few through addnode=x.x.x.x:8333 but still it doesn't seem to connect easily to more than 10 peers.

Any ideas how to get more peers to connect to the node?

Also I was wondering whether there shouldn't be field or some way to show when one finds block! Otherwise it could take long time before you realize you actually found one.

Thanks

Are you fully synced? When I was syncing it would max at 10 for me but once fully synced I'm getting the 32

bluudz

full member

Activity: 215

Merit: 116

Why so serious?

Hey everyone.
Very happy with my Apollo 2 so far. Only thing I'm a bit struggling with is to get node to connect to more peers. Any workaround? I did add quite a few through addnode=x.x.x.x:8333 but still it doesn't seem to connect easily to more than 10 peers.

Any ideas how to get more peers to connect to the node?

Also I was wondering whether there shouldn't be field or some way to show when one finds block! Otherwise it could take long time before you realize you actually found one.

Thanks

TIRMINE

jr. member

Activity: 123

Merit: 4

Anyone know if there is a way to adjust the difficulty settings when renting hash and pointing to the Apollo?

zeekmine

newbie

Activity: 3

Merit: 0

Anyone having problems with the solo miner stopping. I have to reboot. It happens every 1 to 3 days. Anyway to debug aside from manually logging into Linux and checking? ? I have the 2.0.5 Apollo II running low speed on the miner and a HTTP connection to a S19. I am testing an a little worried about hooking up more to it. Thanks.

PennyBit

jr. member

Activity: 7

Merit: 0

Quote from: jstefanop on July 24, 2024, 01:22:26 PM

Quote from: PennyBit on July 23, 2024, 05:32:21 PM

Quote from: MakerAZ on July 19, 2024, 08:13:04 AM

Hello!

I've recently got my Futurebit Apollo II Full Node BTC Miner.
I have some questions:

1) What type of BTC wallet address does Apollo II Solo Miner support? Does it support bc1 address?
2) What software Apollo II does use for BTC Mining? Is it CGMiner?
3) Is it possible to install custom built CGMiner onto Apollo II BTC Miner? if yes, what are the steps?

Thank you!

1) I've used several bc1 addresses and they've all worked fine. You shouldn't have a problem.
2) Interesting question that I really can't answer with much knowledge. Although, it would be interesting to know if you could take, for instance, an R909 pod miner and connect it to the USB port on the Apollo 2 full node and run it. But I'm just thinking out loud. Anyway, I do know that CGMiner will allow a command-line interface so as to configure various mining configurations but I haven't found much yet in the way of that sort of access on AP2. It seems to be all accessed via the interface. Now, I should state that I haven't nosed around much inside the Linux-side files at this point and would say that if you decide to do that, beware.
3) See above.

All addresses are supported except the longer segwit and taproot addresses (forgot the script address names of the top of my head but all legacy, and segwit addresses that are 42 char I believe are currently supported for solo mining).

Apollo uses a custom firmware that is not cgminer based. Yes you could connect any other USB based miner to the apollo to run in the backend (obviously would not show up in the GUI).

Most miner options are exposed in the GUI, but if you want to see all of them and tinker just go to binary directory (/opt/apolloapi/backend/miner) and ./futurebit-miner --help

Thanks jstefanop. Good info to know.

jstefanop

legendary

Activity: 2174

Merit: 1401

Quote from: PennyBit on July 23, 2024, 05:32:21 PM

Quote from: MakerAZ on July 19, 2024, 08:13:04 AM

Hello!

I've recently got my Futurebit Apollo II Full Node BTC Miner.
I have some questions:

1) What type of BTC wallet address does Apollo II Solo Miner support? Does it support bc1 address?
2) What software Apollo II does use for BTC Mining? Is it CGMiner?
3) Is it possible to install custom built CGMiner onto Apollo II BTC Miner? if yes, what are the steps?

Thank you!

1) I've used several bc1 addresses and they've all worked fine. You shouldn't have a problem.
2) Interesting question that I really can't answer with much knowledge. Although, it would be interesting to know if you could take, for instance, an R909 pod miner and connect it to the USB port on the Apollo 2 full node and run it. But I'm just thinking out loud. Anyway, I do know that CGMiner will allow a command-line interface so as to configure various mining configurations but I haven't found much yet in the way of that sort of access on AP2. It seems to be all accessed via the interface. Now, I should state that I haven't nosed around much inside the Linux-side files at this point and would say that if you decide to do that, beware.
3) See above.

All addresses are supported except the longer segwit and taproot addresses (forgot the script address names of the top of my head but all legacy, and segwit addresses that are 42 char I believe are currently supported for solo mining).

Apollo uses a custom firmware that is not cgminer based. Yes you could connect any other USB based miner to the apollo to run in the backend (obviously would not show up in the GUI).

Most miner options are exposed in the GUI, but if you want to see all of them and tinker just go to binary directory (/opt/apolloapi/backend/miner) and ./futurebit-miner --help

PennyBit

jr. member

Activity: 7

Merit: 0

Quote from: MakerAZ on July 19, 2024, 08:13:04 AM

Hello!

I've recently got my Futurebit Apollo II Full Node BTC Miner.
I have some questions:

1) What type of BTC wallet address does Apollo II Solo Miner support? Does it support bc1 address?
2) What software Apollo II does use for BTC Mining? Is it CGMiner?
3) Is it possible to install custom built CGMiner onto Apollo II BTC Miner? if yes, what are the steps?

Thank you!

1) I've used several bc1 addresses and they've all worked fine. You shouldn't have a problem.
2) Interesting question that I really can't answer with much knowledge. Although, it would be interesting to know if you could take, for instance, an R909 pod miner and connect it to the USB port on the Apollo 2 full node and run it. But I'm just thinking out loud. Anyway, I do know that CGMiner will allow a command-line interface so as to configure various mining configurations but I haven't found much yet in the way of that sort of access on AP2. It seems to be all accessed via the interface. Now, I should state that I haven't nosed around much inside the Linux-side files at this point and would say that if you decide to do that, beware.
3) See above.

Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 23. (Read 50765 times)