docs/pithead-integration.md § "Stratum over TLS (optional)" still says stack-side TLS "hasn't shipped yet" (tracking pithead#261). It shipped: pithead's docs/workers.md documents p2pool.stratum_tls as live, and the production stack this was verified against serves stratum with TLS on and a pinnable self-signed cert today.
While in there: pithead's workers.md says the rig fields are "prompted at setup" — RigForge's first-run prompt (ensure_config_exists, ~294-333) asks only pool URL + stratum password; TLS + fingerprint are hand-edited into config.json and applied. Both docs should tell the same true story: TLS available, config-file-not-prompt on the rig side. (The pithead half of this drift is being fixed in the pithead repo.)
docs/pithead-integration.md§ "Stratum over TLS (optional)" still says stack-side TLS "hasn't shipped yet" (tracking pithead#261). It shipped: pithead's docs/workers.md documentsp2pool.stratum_tlsas live, and the production stack this was verified against serves stratum with TLS on and a pinnable self-signed cert today.While in there: pithead's workers.md says the rig fields are "prompted at setup" — RigForge's first-run prompt (ensure_config_exists, ~294-333) asks only pool URL + stratum password; TLS + fingerprint are hand-edited into config.json and applied. Both docs should tell the same true story: TLS available, config-file-not-prompt on the rig side. (The pithead half of this drift is being fixed in the pithead repo.)