RPC2026-02-09_020

RPC Standards #020

2026-02-09 5 decisions 114 transcript lines

Follow along

Ask about this call

Answered from this call's summary and transcript only.

AI-generated — verify against the recording.

Organizational:
- ·Host absent; versioning and stale PR decisions postponed to next meeting — 00:05:25
Api Standardization:
- ·Uncle-related methods (execution-apis#445) may be deprecated; non-deterministic and not required post-merge — 00:08:05
- ·Build BlockV1 testing RPC method (execution-apis#747) spec drafted; Geth implementation ready for review — 00:12:05
- ·Debug namespace tracing methods need standardization across clients — 00:16:39
- ·debug_setHead method varies across clients; requires standardization (naming, parameter format) — 00:17:04
Versioning And Releases:
- ·Version releases blocked on cleaning outdated/stalled PRs from 2023 — 00:05:55

•All EL teams — Review Build BlockV1 RPC method PR (execution-apis#747) for cross-client feedback — 00:12:23
•Execution-apis maintainers — Standardize debug_setHead method naming and parameter format across clients — 00:17:04

Uncle-related methods (execution-apis#445) may be deprecated; non-deterministic and not required post-merge
Uncle-related methods may be deprecated due to being non-deterministic and not required post-merge.
Build BlockV1 testing RPC method (execution-apis#747) spec drafted; Geth implementation ready for review
Build BlockV1 testing RPC method spec is drafted and ready for review.
Debug namespace tracing methods need standardization across clients
Debug namespace tracing methods need standardization across clients.
debug_setHead method varies across clients; requires standardization (naming, parameter format)
debug_setHead method requires standardization across clients.
Version releases blocked on cleaning outdated/stalled PRs from 2023
Version releases are blocked until outdated and stalled PRs from 2023 are cleaned.