docs: drop implemented RPC endpoints from the near-future roadmap#439
Conversation
…roadmap The RPC API server now exposes chain-data endpoints (states, blocks, checkpoints, fork choice), so this item no longer belongs in the list of upcoming features.
🤖 Kimi Code ReviewThis is a documentation-only change removing a completed or deprioritized roadmap item. The diff is clean and presents no technical issues. Specific observations:
Suggestions:
No security, correctness, or performance concerns identified in this documentation update. Automated review by Kimi (Moonshot AI) · kimi-k2.5 · custom prompt |
🤖 Codex Code ReviewNo findings. The diff only removes a roadmap bullet from README.md. It does not touch consensus logic, networking, SSZ, signature handling, or any executable Rust code, so I do not see correctness, security, performance, or maintainability risks in this PR. Residual risk is effectively none beyond documentation accuracy. Automated review by OpenAI Codex · gpt-5.4 · custom prompt |
🤖 Claude Code ReviewThe diff is a single-line documentation removal. Here's the review: PR Review:
|
🗒️ Description / Motivation
The roadmap's "near future" section still listed RPC endpoints for chain data consumption (#75) as upcoming work. The RPC API server already exposes chain-data endpoints (finalized state, blocks, headers, justified checkpoint, fork choice), so this item no longer belongs in the upcoming-features list.
What Changed
README.md: removed the Add JSON-RPC endpoints for blocks #75 RPC endpoints line item from the near-future features list.Correctness / Behavior Guarantees
Tests Added / Run
Related Issues / PRs