How to connect Bitaxe if you are running a public pool instance in Umbrel and using tail scale

To answer this question, if you already have an umbrella running tail scales, it’s mostly a fight. Once you have installed the tail scale and the Bitcoin node is fully synced, you can start Bitaxe and Public-Pool.

The documentation seems pretty sparse right now, but if you follow it, it seems to work well. To run a public pool from umbrella, install that add-on and then use “umbrel.local” in the public pool settings as the address of the TCP+Stratum user, port number: 2018, and Bitcoin node (which can be found from Umbrel’s Lightning Node add-on app by selecting “Deposit” in the “Bitcoin Wallet” section). You can use a different Bitcoin address for improved security. It provides the easiest “start” way to minify to your node’s address.

Once this is done, make sure your settings have been changed to use the BTC address of your umbrella. Note that finding Axeos webpage is as easy as checking what the new IP address is to see the Bitaxe output, as after updating your Bitaxe WiFi settings and using your own WiFi network, you will get a new IP address assigned by your router or DHCP server. Enter that IP address in your web browser and the Axeos web page will load immediately. After updating the BTC address of the Axeos web page, save it and restart Bitaxe.

Now this does not mean you are earning the SAT you are mining in your pool – that only happens if you are lucky enough in a pool of Bitaxe rigs to hit the solution that earns 3.125 BTC every 10 minutes. Due to the advantages of incremental SATS, it is necessary to minify directly into a centralized mine pool. But that means that if you add proof of work to the larger Bitcoin community and other large-scale mining operations go down temporarily or permanently, we are all contributing to the decentralized value of Bitcoin by continuing to find solutions and enjoy rewards. Additionally, the added hash power makes it increasingly difficult for state governments to take more than 51% of their total hash power.