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.

Time + luck.

In general your best share should trend towards total shares submitted.

On the top you will see "Accepted Shares" this is the total work submitted to the solo pool. In a perfect world this would match your "Best Share".

Since bitcoin mining is completely random your best share is a totally random number. If you're unlucky it will be lower than total work submitted, and if you are lucky it will be greater.

You can get super lucky and get a 1T share which would take years of submitted work to "catch up" too.

And then you can hit the jackpot of course!

Has anyone hit near 1T on their Apollo II yet? Would be cool for you guys to post your best shares. Think highest we have seen is about 500B.

Also thinking about gamifying the Solo Pool and anonymously submit your best share for ranking on a site (and possibly give out prizes bases on best share as a cool incentive to solo mine without finding blocks).

Of course this would be opt in to collect this data and open source(and it would all be hashed data with no wallets or any personal data other than best share and maybe hashrate collected) but if you guys are interested might start working on it for 2.2 release.

This would also be a cool way to public display the state of the "FutureBit" hashrate network and show the impact all of you are having!

What is disconnecting the network (are you hardwired or running on wireless?) , is it the internal node, internal miner, external miner (connected via USB) or network connected miner (on the LAN or coming through the WAN) ??

Are you seeing more than 12 connections to the node?

I have several PH remotely and locally mining through to my Apollo II full node with no issues at all. My node is hardwired though.

I highly recommend going hardwired if you are solomining to reduce network latency.

Also you may just want to actually shut the Apollo II down fully for a few minutes and restart and let the services come up gracefully without clicking on things. If that doesn't work I would reflash to play it safe.

Unfortunately not but I do know its a work in progress.

I know this was requested by me to be fixed in the next release. Hopefully we will see this soon!

Sounds like you don't have the port forwarding set correctly in your router to be honest.

The forwarding of port 3333 will be used for the external stratum connections / mining pool connectivity.

So if you forward port 3333 from your WAN to your Apollo's internal LAN IP then you should be able to connect miners from outside your LAN to stratum+tcp://YOURPUBLICIP:3333 or stratum+tcp://YOURDDNSDOMAINNAME:3333 .

You can test your IP address and confirm if the port is open through your router here just make sure you change the port to 3333 for testing: https://www.yougetsignal.com/tools/open-ports/

8332 is the port you need to open for the node to communicate and connect up to 32 connections. If you don't see more than 28 connections to your node then this is also not configured properly.

Hope this helps.

You must enable port forwarding regardless!

Yes, if ddns is available, then 100% use the domain they provide with :3333 at the end.

Give Compass that ddns info as your stratum, but make sure you include the :3333 at the end of the ddns domain.

You must enable port forwarding regardless!

Yes, if ddns is available, then 100% use the domain they provide with :3333 at the end.

Give Compass that ddns info as your stratum, but make sure you include the :3333 at the end of the ddns domain.

I have done this personally and here is what you can try.

Steps 1 -4 assume you are using home internet service where your IP address is dynamic and not a static IP

First step:
You will need to make sure you have port forwarding enabled on your router for port 3333 to go to the internal ip address of your Apollo.
You can find this by logging into the gui and clicking on the solo mining option it tells you the internal ip as well as that its port 3333.
(Some routers need a full reboot after setting this configuration)

Second step:
Find your public IP address you can use tools like whatismyip.com

Third step:
Tell Compass to use the stratum code stratum+tcp://YOURPUBLICIP:3333

You can tell the to use your bitcoinaddress.workername with a password of x

Once they do then you then should see your miners hashrate show up on your Apollo / ckpool.

Fourth step (Optional):
If you are using a dynamic IP address look to see if your router offers DDNS (Dynamic DNS) if so configure it with so that you can always route to your public ip in case it changes.