docs(readme): expand roadmap with near-term priorities

[pablodeymo]

Motivation

The README's "Incoming features" section listed only a single item. This updates it to reflect our near-term roadmap, in priority order, and links to the blogpost where we lay out our thinking.

Description

• Rename Incoming features → Incoming features / Roadmap
• Link to the ethlambda devnet-5 and beyond blogpost
• Replace the single roadmap entry with a prioritized list:
  • Optimize block building
  • Store the state-diff in the database
  • Prototype Goldfish + RLMD GHOST + BFT — devnet-6
  • Integrate with execution clients, in particular ethrex — devnet-7
  • Replace libp2p with the experimental ethp2p (being ported to Rust)
  • Add a guest program and ZK proving of the STF
  • Rewrite the STF in a concrete language to enable formal verification

[github-actions]

🤖 Kimi Code Review

The diff provided contains documentation changes only (README.md). There are no Rust code changes affecting consensus logic, cryptography, state transitions, or networking to review against the technical criteria specified.

Summary of changes:

• Section header updated from "Incoming features" to "Incoming features / Roadmap" (line 135)
• Added reference to blogpost about future development plans (line 138)
• Expanded roadmap with specific priorities: block building optimization, state-diff storage, Goldfish/RLMD-GHOST/BFT prototype, ethrex integration, ethp2p migration, and formal verification goals (lines 142-148)

Review: The documentation changes are clear and accurate. The roadmap items appropriately reflect Ethereum consensus development priorities (e.g., 3SF-mini fork choice research, XMSS signature schemes, ZK-STF proving). No issues identified.

Note: If this PR contains additional commits with code changes not shown in this diff, please provide the complete diff for technical review of consensus-critical components.

---

Automated review by Kimi (Moonshot AI) · kimi-k2.5 · custom prompt

[github-actions]

🤖 Codex Code Review

No findings.

The diff in /tmp/pr_diff.txt only changes the roadmap text in README.md, specifically lines 135-147. I did not see any Rust, consensus, networking, SSZ, signature, or state-transition code changes, so there is nothing here that affects fork choice, attestation handling, justification/finalization, XMSS verification, memory safety, or performance-critical execution paths.

Residual note: this review is scoped to the provided diff. If PR 463 is expected to contain code changes beyond README.md, the diff artifact appears incomplete.

---

Automated review by OpenAI Codex · gpt-5.4 · custom prompt

[greptile-apps]

Greptile Summary

This PR expands the README's roadmap section from a single entry to a prioritized 7-item list, renames the section heading to "Incoming features / Roadmap", and adds a link to the team's devnet-5-and-beyond blogpost.

• Replaces the lone "Add guest program and ZK proving of the STF" entry with a full ordered roadmap covering block building, state-diff storage, Goldfish/RLMD GHOST/BFT prototyping, ethrex integration, ethp2p migration, ZK proving, and formal verification.
• Adds inline links to the ethrex and ethp2p GitHub repos for the relevant items, and preserves the original issue link for the ZK proving entry.

Confidence Score: 5/5

Documentation-only change with no impact on code behavior; safe to merge.

The change is limited to README.md and adds a prioritized roadmap list with links to relevant repos and a blogpost. No logic, configuration, or build artifacts are touched.

No files require special attention.

Important Files Changed

Filename	Overview
README.md	Expands "Incoming features" section into a prioritized 7-item roadmap with a blogpost link; purely documentation, no code changes

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Incoming features / Roadmap] --> B[1. Optimize block building]
    B --> C[2. Store state-diff in database]
    C --> D["3. Prototype Goldfish + RLMD GHOST + BFT — devnet-6"]
    D --> E["4. Integrate with ethrex — devnet-7"]
    E --> F[5. Replace libp2p with ethp2p]
    F --> G[6. Add guest program + ZK proving of STF]
    G --> H[7. Rewrite STF for formal verification]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Incoming features / Roadmap] --> B[1. Optimize block building]
    B --> C[2. Store state-diff in database]
    C --> D["3. Prototype Goldfish + RLMD GHOST + BFT — devnet-6"]
    D --> E["4. Integrate with ethrex — devnet-7"]
    E --> F[5. Replace libp2p with ethp2p]
    F --> G[6. Add guest program + ZK proving of STF]
    G --> H[7. Rewrite STF for formal verification]

Loading

_{Reviews (1): Last reviewed commit: "Expand the roadmap section in the README..." | Re-trigger Greptile}

[github-actions]

🤖 Claude Code Review

---

Review — PR 463: docs(readme): expand roadmap with near-term priorities

This PR is a README-only documentation edit: it renames the "Incoming features" section, adds a blogpost link, and replaces a single roadmap bullet with a prioritised list of seven items. No Rust code is touched.

No code correctness, security, performance, or Rust-idiom findings apply.

One minor content observation worth the author's attention:

README.md:127 vs. README.md:143 — mild inconsistency between the pq-devnet-6 section and the new roadmap.

The pq-devnet-6 section (line 127) still reads "no features have been specified yet", while the new roadmap (line 143) now lists "Prototype Goldfish + RLMD GHOST + BFT — devnet-6" as a concrete entry. A reader scrolling through will see a contradiction. Consider updating line 127 to reference the roadmap item, or removing the "not yet specified" qualifier, so both sections agree.

Everything else looks good: the em-dash usage is consistent, the Markdown formatting is clean, all three external links (lambdaclass/ethrex, ethp2p/ethp2p, the blogpost) follow the correct pattern, the GitHub issue link for the ZK proving item is preserved, and the priority ordering matches the PR description.

---

Automated review by Claude (Anthropic) · sonnet · custom prompt