RPC2026-02-23_021

RPC Standards #021

2026-02-23 4 decisions 527 transcript lines

Transcript

At a glance

Max use gas (PR #746) deferred from V1; not ready for initial release
X-error-groups won't be embedded in published OpenRPC; validation at build time only
GraphQL tests and potentially GraphQL API itself to be deprecated/removed
Stalled PRs (tx pool, receipt proof, etc.) require EIP process; close old PRs
V1.0.0 release after test regressions fixed and client pass rates restored

Detailed notes

Stalled Prs

  • •GraphQL API considered unmaintained; removal being evaluated00:56:33
  • •Old stalled PRs should be recreated fresh without baggage01:00:01
  • •New proposals should be introduced one-per-ACDE for better voting success01:03:44

Versioning Proposal

  • •V1.0.0 versioning proposal covers 71 methods through Cancun fork00:02:13
  • •GitHub release process can proceed; Felix will create V1 release00:06:05
  • •Test runner will target released version instead of latest00:08:36
  • •Block timestamp added to transaction object; tests need updating00:09:00
  • •Documentation versioning requires GitHub Actions updates for version selector00:11:00

Testing Infrastructure

  • •Current conformance testing setup works well; tests tied to specific chain state00:48:45
  • •I.O. file interpreter library may move to execution-apis repository for reuse00:51:06

Error Code Standardization

  • •X-error-groups extension enables native validation without additional tooling00:31:41
  • •Spec generation now uses Go tools; translation validates errors during build00:36:25
  • •Error groups won't be embedded in final OpenRPC JSON; validation moves to build process00:39:27

Action items

  • •Update RPC tests to include block timestamp in transaction objectFelix
  • •Implement docs versioning with version selector in GitHub ActionsZane/Documentation team
  • •Update Go toolchain to support error code validation during spec buildFelix/EF team
  • •Recreate stalled PRs as fresh proposals; introduce one per ACDE callMercy

Agenda

From the call issue #1943Show

Agenda

1. Versioning Proposal Review

Proposal Document: Execution APIs v1.0.0 - Versioning Proposal, ethereum-magicians

Review the v1.0.0 versioning proposal and gather team input on:

  • Overall scope agreement (71 methods, through Cancun fork)
  • PRs to merge before tagging (#753, #742)
  • Deferred items list approval

2. Open Questions Requiring Team Decision

QuestionOptionsRelated Issue
Error code standardizationA) Before v1 (delays release) B) Defer to v2#658, #650
Test coverage gap (11 methods)A) Block v1 until complete B) Release with gaps#737
eth_simulateV1 maxUseGasA) Include in v1 B) Defer to v1.1#746
EIP-1898 complianceA) Full compliance before v1 B) Document current state#713

3. Open Issues

IssueTitlePriority
#690API versioning via GitHub releases/tagsCritical
#658Standardize JSON-RPC Error codesCritical
#713Fully apply EIP-1898 in specsHigh
#737Missing Test Coverage for 11 methodsMedium
#663GenericTransaction Should Contain dataMedium

4. Open PRs

PRTitleAuthorStatus
#753Fix: engine nits-Ready for merge
#747Add testing_buildBlockV1 RPC MethodPandasNeeds Marius review
#746Add maxUseGas field to eth_simulateV1-Discussion needed
#742test(debug_getRawReceipts): post-Byzantium block-Ready for merge
#735EIP-8025-Deferred
#726Add EIP-7928 Block-level Access Lists-Deferred

5. Outdated / Stalled PRs

Review and decide: close or revive?

Identified in previous meeting - several PRs from 2023 may be abandoned

Key decisions

  • Max use gas (PR #746) deferred from V1; not ready for initial release

    Deferred due to not being ready for the initial V1 release
  • X-error-groups won't be embedded in published OpenRPC; validation at build time only

    Validation will occur during the build process instead of being embedded in OpenRPC
  • GraphQL tests and potentially GraphQL API itself to be deprecated/removed

    GraphQL tests and API may be deprecated or removed
  • Stalled PRs (tx pool, receipt proof, etc.) require EIP process; close old PRs

    Stalled PRs need to go through the EIP process and old PRs should be closed

AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.