[Tracker] Pluto ↔ Charon port — master tracker

[varex83]

Pluto ↔ Charon port — master tracker

🎯 Goal

Fully port charon run to Pluto. Everything tracked here exists to land pluto run at functional parity with charon run — a runnable distributed-validator node that boots, joins peers, runs DKG-derived keyshares, and produces valid signed duties end-to-end.

Anything that does not directly serve pluto run parity is out of scope for this tracker.

Status

This issue tracks the Go → Rust port of Charon into Pluto. Work is grouped into three parallel tracks, plus integration anchors. Track ownership can scale up or down as the team changes — labels and sub-issue links are the source of truth, not fixed assignments.

The detailed plan (phases, calendar, risks) lives in the team Slack thread; this issue holds the issue graph.

Track epics

The three track epics are wired as sub-issues of this tracker — see the GitHub sub-issues panel for live progress bars.

• [Epic] Track A — Duty pipeline + consensus #395 — Track A — Duty pipeline + consensus
• [Epic] Track B — Validator API + tracker #396 — Track B — Validator API + tracker
• [Epic] Track C — Orchestration + CLI #397 — Track C — Orchestration + CLI

Integration milestones

• Phase 1 gate: QBFT strategysim parity green (core/qbft async rewrite + core/consensus)
• 🏁 Final goal / Phase 4 gate: pluto run boots a 4-node compose and runs one slot end-to-end → Implement cmd/run — main node binary #403 (cmd/run) closed implies this tracker can close

Conventions

• One PR per Go module (preserve the charon ↔ pluto bijection)
• Read the Go source before writing Rust (per AGENTS.md)
• Cross-track review on every PR
• cargo test --workspace --all-features must be green at every integration sync point

Labels

• track:duty-pipeline
• track:validator-api
• track:orchestration-cli

Use these to filter issue lists per track.

[emlautarom1-agent]

📊 Progress audit — 2026-06-15

A full source-level audit of Pluto vs Charon (commits on main, open PRs, and tokei on both trees) shows the port is further along than this tracker reflects — the main gap is bookkeeping, not code. Per-issue audit comments have been added to each affected issue; this is the rollup.

Legend: ✅ merged · 🟡 open PR / in review · 🔴 not started · ⏸ off the single-slot critical path

Critical path to pluto run (Phase-4 gate #403)

The minimal end-to-end slot needs exactly the 10 core.Wire components (core/interfaces.go:337-357) + shared infra (eth2api✅, deadliner✅, p2p✅, gater).

Module	Status	Charon non-test LOC
core/scheduler #176	🟡 PR #466 (in review)	664
core/fetcher #172	🟡 PR #454 (draft)	431
core/bcast #170	🟡 PR #480 (draft)	522
core/consensus controller #398	🟡 PR #471 (in review)	201
core/gater #399	🔴	45
core/validatorapi #180	🟡 ~80% (PRs #457/#459/#460/#462)	2815
core/dutydb #171 · aggsigdb #169 · parsigdb · parsigex · sigagg #178	✅	—
app/app.go wiring #402	🔴	936
cmd/run #403 🎯	🔴	177

Parity polish (⏸ — NOT required for the first end-to-end slot)

CurrentConsensus() defaults to QBFT v2.0, and tracking/monitoring/sse are wrappers/observability, so these can be stubbed or deferred for the gate:
core/tracker #179 (🟡 ~done) · core/priority #177 (🔴 668) · core/infosync #173 (🔴 149, needs priority) · consensus/metrics #62 (🟡 PR #470) · consensus/mocks #39 · app/health #68 · app/sse #183 · app/monitoringapi #400 · app/vmock #401 · app/tracer #47 (🟡 largely covered by crates/tracing) · app/forkjoin #41 · app/stacksnipe #71 · app/protonil #46

Independent CLI (does not block run)

cmd/exit #404–409 (obolapi ✅) · cmd/combine #181 (cluster/manifest ✅) · cmd/addvalidators #410 (dkg ✅). Note #411/#412 are mis-scoped (see those issues).

Hygiene recommendations

• Close issues that are done but still open: Implement core/sigagg #178 core/sigagg (793 Rust LOC, 0 stubs), Implement cluster/manifest #199 cluster/manifest (fully ported). Verify Implement core/tracker #179 core/tracker (~3,974 Rust LOC) and close once parity-checked.
• Stale states: every module with an open PR above is "open" with no status; the epic progress bars therefore understate reality. Closing on-merge would fix the bars.
• Boilerplate issues (Implement core/bcast #170/Implement core/fetcher #172/Implement core/scheduler #176/Implement core/priority #177/Implement core/sigagg #178/Implement core/tracker #179/Implement core/validatorapi #180, created 2026-01-28) lack scope/deps/LOC; the per-issue audit comments supply that detail.
• Re-scope/clarify: Implement core/gater #399 (DutyGater vs libp2p ConnGater), Implement cmd/manifest_tools #411 & Implement cmd/debug_tools #412 (Charon helpers, not commands).
• Untracked-but-done pipeline pieces: core/parsigdb (497 LOC) and core/parsigex (867 LOC) are merged but have no sub-issue — add for graph completeness.

---

Automated progress audit (2026-06-15). New comment only — no existing issue content was modified.