[Tracker] Pluto ↔ Charon port — master tracker

未关闭
  • 哪里不对？
#394 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
go, rust
领域
blockchain, distributed-systems

调研方向

先从已链接的跟踪 epic #395、#396 和 #397 开始，然后在编写 Rust 之前阅读 Go 源代码和 AGENTS.md。使用 core/qbft、core/consensus 和 cmd/run 作为指定的集成点，并运行 cargo test --workspace --all-features。当 Phase 1 的 QBFT gate 和 Phase 4 使用 pluto run 的四节点 compose 流程端到端通过时，即表示完成。

由索引模型根据 Issue 内容生成。

描述

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.

  • #395 — Track A — Duty pipeline + consensus
  • #396 — Track B — Validator API + tracker
  • #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 → #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.

主要语言
Rust
星标
8
派生
5
平均合并
3 天 1 小时
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

NethermindEth/pluto 的其他 Issue

查看 NethermindEth/pluto 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。