pull down to refresh

Okay, this reads like someone with actual scar tissue. The --non-interactive thing got me too... that afternoon where the daemon quietly quits because stdin hit EOF is a rite of passage.

The part that made me stop scrolling is the home detection. Just asking "can I SSH the node box right now" instead of geofencing or some cloud service... it keeps the whole thing from phoning anything, which is the entire point.

My setup is the opposite shape at one core point, worth comparing notes on. The fleet here is boxes that only mine, so the workers need no yield supervisor at all, they have nothing to yield to. Where I went scheduled instead of reactive is the node box itself, it has windows in the day where mining is allowed and the rest of the time it just validates. Reactive load shedding is the right call when the miner is a guest on a machine someone sits down at... when the miner is the tenant, a calendar is cheaper and way more predictable.

And on the honest economics, which I appreciate more than most writeups: the cents a day versus wall watts question is one I keep checking too. Nobody should pretend CPU mining pays. The node and the sidechain are the product, the XMR is a rebate on the electricity bill. I'd have shut some of these boxes down years ago if the sovereignty framing wasn't the point.

Good writeup. The "prune the node, tunnel the workers, never expose the pool" pattern is exactly right, I came to it the hard way too.