docs(faq): update the "vs. Gupax" comparison — Gupax now bundles node/proxy/XvB

[VijitSingh97]

Summary

The "vs. Gupax" subsection of docs/faq.md is out of date. It described Gupax as a GUI for "P2Pool + XMRig" on a single machine, linked to the old hinto-janai/gupax repo, and (in an interim draft) attributed XvB to a "Gupaxx fork." Gupax has changed materially and several of the things we framed as Pithead-only are now table stakes for Gupax too.

Verified against the current upstream README at https://github.com/gupax-io/gupax on 2026-06-15.

What's stale / wrong

• Link: pointed at hinto-janai/gupax. Canonical repo is now gupax-io/gupax (description "GUI Uniting P2Pool And XMRig", active, default branch main).
• Feature set: described as "P2Pool + XMRig" only. Gupax now also bundles/manages a local Monero node, a proxy for external miners, and a built-in XvB raffle algorithm.
• No fork-lineage editorializing: do not claim XvB arrived "via the Gupaxx fork being folded back in." The upstream README makes no such statement, and the signals point the other way (donation address, the #xmrvsbeast Matrix room, contact email, and the librejo mirror at Ecosystem/gupaxx). Describe Gupax as it documents itself.

Verified current facts about Gupax (gupax-io/gupax)

• Cross-platform desktop GUI — Windows / macOS / Linux; also a --daemon headless mode.
• Manages (Node + Proxy + XvB tabs hidden by default; P2Pool + XMRig on by default): its own monerod, external miners via a bundled proxy, and an XvB hashrate-splitting algorithm.
• Tor: not in the official app — only a community Docker image (libre7/gupax-docker) offers an optional Tor hidden service.
• No Tari merge-mining.

Remaining genuine Pithead differentiators (lead the comparison with these)

• Form factor: always-on multi-container server stack (9 Docker services) on a dedicated Linux box, vs. a single desktop app you launch on your mining machine.
• Tor-first by default — onion addresses for Monero / Tari / P2Pool out of the box.
• Tari merge-mining — a second payout for the same hashes (Gupax has none).
• Node-down worker failover, hardened / version-pinned containers, and a LAN web dashboard.
• Acknowledge the overlap honestly: both can run your own node, take external miners, and split hashrate to XvB.

Acceptance criteria

• docs/faq.md "vs. Gupax" section links to gupax-io/gupax and matches the verified facts above.
• Comparison leads with form factor + the two clean differentiators (Tor-first, Tari) and acknowledges the node/proxy/XvB overlap.
• No unverified fork-lineage claims.
• Re-verify against the upstream README at time of writing — Gupax is actively developed and may have moved again.

A draft rewrite already exists and can seed the PR; it should still be re-verified against upstream before merge.

[VijitSingh97]

Done — docs/faq.md 'vs. Gupax' now links gupax-io/gupax, describes the bundled node/proxy/XvB, and notes no built-in Tor / no Tari. Matches acceptance.