RPC2026-04-20_025

RPC Standards #025

2026-04-20 4 decisions 428 transcript lines

Transcript

At a glance

TXPool namespace PR merged despite expected test failures due to non-deterministic behavior
OpenRPC document version will track execution-apis release tags via CLI flag
Engine API changes must be discussed on ACDE/ACDC, not RPC Standards calls

Detailed notes

Client Updates

  • •Geth hasn't implemented standardized error codes yet; tests will warn only00:11:03
  • •TXPool content/status tests merged; will fail initially due to non-deterministic content00:18:00

Organizational

  • •Versioning approach: GitHub releases with pre-compiled artifacts, no caching issues00:19:15
  • •OpenRPC version will match execution-apis tag; added via CLI flag not YAML00:23:58
  • •Assembled spec branch used by Flashbots and downstream consumers00:31:41

Testing Progress

  • •Initial negative error code tests PR ready; includes replacement transaction underpriced00:06:12
  • •Test fixtures auto-generated; currently return Geth error codes with overrides00:08:20

Critical Infrastructure

  • •EF capabilities PR needs ACDE review; models client resource availability00:32:02
  • •Delete strategy field controversial; may make optional or rename to retention policy00:32:30
  • •Alternative: subscription-based availability notifications instead of static deletion strategy00:40:05

Action items

  • •Create Geth PR for standardized error codes implementationMercy or community contributor
  • •Present EF capabilities PR (755) to ACDE for client team feedbackMercy
  • •Review and comment on EF capabilities PR optional fields proposalAll client teams

Agenda

From the call issue #2029Show

Key decisions

  • TXPool namespace PR merged despite expected test failures due to non-deterministic behavior

    The TXPool namespace PR was merged with the understanding that tests would initially fail due to non-deterministic content.
  • OpenRPC document version will track execution-apis release tags via CLI flag

    Standardizing the versioning of OpenRPC documents to align with execution-apis release tags using a CLI flag.
  • Engine API changes must be discussed on ACDE/ACDC, not RPC Standards calls

    Clarification of governance scope, moving Engine API discussions to ACDE or ACDC meetings.
  • Versioning approach: GitHub releases with pre-compiled artifacts, no caching issues

    Agreement on using GitHub releases for versioning to avoid caching problems.

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.