v2.x - post-GA

Open

No due date

•Last updated Oct 12, 2026

Appliance fast-follows that ship after the v2 GA cut: parity options C/E/F (#911/#912/#913), fleet tooling, and diagnostics. Deliberately outside the GA gate per the #786 decision record.

20% complete

Fleet descriptor editing behind the approval channel
p2pool-starter-stack/pithead#912 · opened on Aug 13, 2026 · v2.x - post-GA
1
Appliance feature parity: everything host-CLI-only is impossible on a shell-less box
p2pool-starter-stack/pithead#786 · opened on Jul 27, 2026 · v2.x - post-GA
4
Master installer image: one stick provisions a Pithead coordinator, a RigForge rig, or both
p2pool-starter-stack/pithead#797 · opened on Jul 31, 2026 · v2.x - post-GA
10
Headless fleet installs cannot choose the target disk — select by serial, never by /dev path
p2pool-starter-stack/pithead#979 · opened on Aug 14, 2026 · v2.x - post-GA
1
First boot is only partially offline: the wizard image is baked, the rest of the stack still pulls
p2pool-starter-stack/pithead#978 · opened on Aug 14, 2026 · v2.x - post-GA
1
Quadlet units lack the healthcheck their compose siblings carry — and must adopt the degrading form when they get it
p2pool-starter-stack/pithead#1217 · opened on Aug 22, 2026 · v2.x - post-GA
1
Caddyfile bind-list building is asymmetric with site-list building — the bridge gateway is excluded from one but not the other
p2pool-starter-stack/pithead#1219 · opened on Aug 22, 2026 · v2.x - post-GA
1
Let rigs on other networks mine over Tor: an opt-in onion for the stratum, default off — plus the appliance rig's half of dialling it
p2pool-starter-stack/pithead#1319 · opened on Aug 23, 2026 · v2.x - post-GA
3
release.sh does not know the appliance exists: the image, the bundle, their checksums and the baked RigForge pin are attached by hand, and nothing refuses a publish without them
p2pool-starter-stack/pithead#1800 · opened on Sep 5, 2026 · v2.x - post-GA
1
doctor --json rows carry no stable check id, so every consumer string-matches prose
p2pool-starter-stack/pithead#1805 · opened on Sep 5, 2026 · v2.x - post-GA
1
Appliance rigs have no remote OS-update path: the A/B install is proven on a rig, but nothing delivers a bundle to a shell-less rig (worker upgrade is RigForge's git path, no rig-side release check, run-from-USB slot layout unmeasured)
p2pool-starter-stack/pithead#1837 · opened on Sep 5, 2026 · v2.x - post-GA
2
[Feature] Tier-4 appliance battery: port off libvirt to plain qemu with conditional acceleration, so a Mac can run the boot phase
p2pool-starter-stack/pithead#2089 · opened on Sep 12, 2026 · v2.x - post-GA
3
KVM: prove local chain continuity across --image-upgrade (full copy-on-write gate)
p2pool-starter-stack/pithead#2225 · opened on Sep 14, 2026 · v2.x - post-GA
2
Unanswered from #1103: does a co-located miner on a reduced-RAM box mine usefully, or thrash? The tier's refusal rests on an argument, not a hashrate measurement
p2pool-starter-stack/pithead#2045 · opened on Sep 10, 2026 · v2.x - post-GA
7
Publish the stratum as an onion service, default off — the server half of #1319
p2pool-starter-stack/pithead#2437 · opened on Sep 19, 2026 · v2.x - post-GA
1
The appliance rig cannot dial an onion stratum: no Tor client on the box, no socks5 in the generated config, and a preflight that cannot reach one
p2pool-starter-stack/pithead#2438 · opened on Sep 19, 2026 · v2.x - post-GA
1
Unmeasured: what Tor costs a *stratum* share
p2pool-starter-stack/pithead#2439 · opened on Sep 19, 2026 · v2.x - post-GA
1
P2Pool parity: every upstream v4.18 flag, console command and data-API field Pithead does not expose (tracker)
p2pool-starter-stack/pithead#2481 · opened on Sep 20, 2026 · v2.x - post-GA
1
p2pool.extra_flags: an allowlisted passthrough so any upstream P2Pool option can be set from config.json, wizard and dashboard
p2pool-starter-stack/pithead#2482 · opened on Sep 20, 2026 · v2.x - post-GA
1
Backup Monero nodes: render multiple --host entries so P2Pool fails over on its own (hosts / next_host)
p2pool-starter-stack/pithead#2483 · opened on Sep 20, 2026 · v2.x - post-GA
1
Mine to a Monero subaddress (--subaddress): the primary-only validation from #250 is no longer required by P2Pool
p2pool-starter-stack/pithead#2484 · opened on Sep 20, 2026 · v2.x - post-GA
1
P2Pool log level: p2pool.log_level (--loglevel) plus the runtime loglevel console command
p2pool-starter-stack/pithead#2485 · opened on Sep 20, 2026 · v2.x - post-GA
1
P2Pool RAM knobs for the reduced-RAM tier: --light-mode (saves 2 GB) and --no-randomx
p2pool-starter-stack/pithead#2486 · opened on Sep 20, 2026 · v2.x - post-GA
1
P2Pool peer controls: --out-peers/--in-peers/--addpeers, the console peer commands, and a peers/bans panel from local/p2p
p2pool-starter-stack/pithead#2487 · opened on Sep 20, 2026 · v2.x - post-GA
1
Onion-only P2Pool peering: wire --no-clearnet-p2p to a config knob (privacy.md names the gap) and always pass --no-upnp
p2pool-starter-stack/pithead#2488 · opened on Sep 20, 2026 · v2.x - post-GA
1

Navigation Menu

v2.x - post-GA

Fleet descriptor editing behind the approval channel

Appliance feature parity: everything host-CLI-only is impossible on a shell-less box

Master installer image: one stick provisions a Pithead coordinator, a RigForge rig, or both

Headless fleet installs cannot choose the target disk — select by serial, never by /dev path

First boot is only partially offline: the wizard image is baked, the rest of the stack still pulls

Quadlet units lack the healthcheck their compose siblings carry — and must adopt the degrading form when they get it

Caddyfile bind-list building is asymmetric with site-list building — the bridge gateway is excluded from one but not the other

Let rigs on other networks mine over Tor: an opt-in onion for the stratum, default off — plus the appliance rig's half of dialling it

release.sh does not know the appliance exists: the image, the bundle, their checksums and the baked RigForge pin are attached by hand, and nothing refuses a publish without them

doctor --json rows carry no stable check id, so every consumer string-matches prose

Appliance rigs have no remote OS-update path: the A/B install is proven on a rig, but nothing delivers a bundle to a shell-less rig (worker upgrade is RigForge's git path, no rig-side release check, run-from-USB slot layout unmeasured)

[Feature] Tier-4 appliance battery: port off libvirt to plain qemu with conditional acceleration, so a Mac can run the boot phase

KVM: prove local chain continuity across --image-upgrade (full copy-on-write gate)

Unanswered from #1103: does a co-located miner on a reduced-RAM box mine usefully, or thrash? The tier's refusal rests on an argument, not a hashrate measurement

Publish the stratum as an onion service, default off — the server half of #1319

The appliance rig cannot dial an onion stratum: no Tor client on the box, no `socks5` in the generated config, and a preflight that cannot reach one

Unmeasured: what Tor costs a stratum share

P2Pool parity: every upstream v4.18 flag, console command and data-API field Pithead does not expose (tracker)

p2pool.extra_flags: an allowlisted passthrough so any upstream P2Pool option can be set from config.json, wizard and dashboard

Backup Monero nodes: render multiple --host entries so P2Pool fails over on its own (hosts / next_host)

Mine to a Monero subaddress (--subaddress): the primary-only validation from #250 is no longer required by P2Pool

P2Pool log level: p2pool.log_level (--loglevel) plus the runtime loglevel console command

P2Pool RAM knobs for the reduced-RAM tier: --light-mode (saves 2 GB) and --no-randomx

P2Pool peer controls: --out-peers/--in-peers/--addpeers, the console peer commands, and a peers/bans panel from local/p2p

Onion-only P2Pool peering: wire --no-clearnet-p2p to a config knob (privacy.md names the gap) and always pass --no-upnp

Issues