<oembed><type>rich</type><version>1.0</version><title>fountainhead wrote</title><author_name>fountainhead (npub1f6…9l55f)</author_name><author_url>https://nostr.now/npub1f6n2pd27gve7fqgkua5n5ssssnmhqnpf2tjg5ae4359dcsuyrm9s89l55f</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>Solo mining newb questions:&#xA;&#xA;I’m running bitcoin core on Umbrel and just installed the public pool app to learn about solo mining. I’ve got a bitaxe pointed to the stratum address of the local public pool instance. &#xA;&#xA;The public pool app can see the bitaxe activity, and I can see the job information being sent to the bitaxe in the bitaxe logs. It’s hashing away (and occasionally overheating), and everything appears to be working fine. &#xA;&#xA;I’m assuming the bitaxe firmware is getting the block template from the public pool Umbrel app. Is this accurate?&#xA;&#xA;If so, is the local public pool app generating its own block template based on my local node, or is it getting it from the ‘larger’ public pool?&#xA;&#xA;Is the local public pool app decreasing the difficulty that’s being sent to my bitaxe, like most pools do?  I’m assuming it is since I can see that many shares have been submitted by the bitaxe. &#xA;&#xA;Is any of this configurable locally?&#xA;&#xA;Is any of this able to be viewed via the CLI?&#xA;&#xA;Appreciate any feedback.</html></oembed>