Auto-register miners with XvB raffle (xvb client) — no manual signup

[VijitSingh97]

Summary

The stack currently never registers miners with XMRvsBeast (XvB). We only (1) mine to the XvB pool with donor_id as the stratum username and (2) read raffle stats via GET .../p2pool_bonus_history.cgi. There is no call to XvB's registration endpoint.

The XvB operator confirmed (via DM) that there is a raffle-miner registration API, and that hitting it is what actually enters a wallet into the raffle — "it will register the wallet address provided it has a share in the p2pool PPLNS window." Without this call, users who enable XvB may be donating/mining but not properly entered.

We should add an auto-registration step to the XvB client so users are entered in the raffle automatically once they have a PPLNS share — no manual signup required.

⚠️ Do not paste the exact endpoint in this public repo. The operator deliberately does not publish this API ("to mitigate abuse"). The full URL is in the maintainer's XvB DM. Reference it only as p2pool_bonus_submit_api.cgi?address=WALLET_ADDRESS when implementing; keep the host/path out of committed code comments and docs where reasonable.

What we know about the API

• It's a GET taking ?address=<full Monero wallet address>.
• It only registers if the wallet has a share in the P2Pool PPLNS window — so calling it before we've found a share is a no-op. We must call it (and likely retry) once a PPLNS share exists.
• It registers the full wallet address (the raffle then tracks the donor by the first-8-char donor_id, which is what we already mine with).

Proposed implementation

• Add a register() (or ensure_registered()) method to the XvB client: build/dashboard/mining_dashboard/client/xvb_client.py — mirror the existing stats call (same requests.get, same Tor SOCKS5 proxy, ~20s timeout).
• Gate on xvb.enabled — never register when XvB is off.
• Only fire once we have a PPLNS share (reuse whatever share-detection the dashboard already has). Before that, skip and retry on the next poll.
• Make it idempotent / safe to repeat: register once on first eligibility, then re-register periodically (e.g. daily) so re-registration with the newer security-token behavior happens automatically and a long-offline miner re-enters cleanly.
• Route over Tor like the stats call — registration sends the full wallet address, so it must not leak over clearnet (consistent with the privacy-egress work, [Epic] Privacy: no clearnet egress outside Tor — close leaks + privacy-first defaults #160/Dashboard: route XvB stats through Tor + gate behind XVB_ENABLED (IP↔wallet leak) #163).
• Log success/failure to the dashboard so a user can see "Registered with XvB ✓".

Acceptance criteria

• With xvb.enabled: true and at least one PPLNS share, the wallet is auto-registered with XvB with no manual step.
• No registration call is made when xvb.enabled: false or before a PPLNS share exists.
• The call is routed over Tor (no clearnet leak of the wallet address).
• Re-registration happens on a sane cadence (idempotent).
• The exact endpoint URL is not committed to this public repo / docs.
• Docs: add a short "you're auto-registered with XvB once you have a share" note (replaces the otherwise-needed manual-registration instructions).

Context / notes

• Today donor_id: auto = first 8 chars of the wallet (computed in the pithead script ~L1764); registration uses the full address, so we'll need the full MONERO_WALLET, not the truncated id.
• Related prior discussion: docs currently say nothing about XvB registration (it was never documented); this issue is the fix.
• See also privacy-egress: [Epic] Privacy: no clearnet egress outside Tor — close leaks + privacy-first defaults #160, Dashboard: route XvB stats through Tor + gate behind XVB_ENABLED (IP↔wallet leak) #163.