RPC2026-10-05_036

RPC Standards #036

2026-10-05 2 decisions 161 transcript lines

Transcript

At a glance

Error codes: positive values use new grouped catalog; negative values retain legacy semantics; no changes to simulate V1
Tracing API does not require an EIP; existing client implementations are sufficient

Detailed notes

Error Codes

  • •Blocker resolved: positive error codes use new grouped catalog; negative codes remain legacy (simulate V1 unchanged)00:16:28
  • •simulate V1 error code unification deferred to simulate V2; no breaking changes to V100:17:37

Tracing Apis

  • •Tracing spec blocked on Geth PRs; Bantag has draft Geth PR but won't finalize until all clients agree00:20:07
  • •Felix's validation script PRs (execution-apis + Hive) are 99% done; minor feedback outstanding before merge00:26:49
  • •Nimbus EL not tracked in tracing compatibility work; Chase to follow up with Bantag00:29:04

Action items

  • •Open PR for unified error code catalog; positive = new grouped, negative = legacySimsonraj Easvarasakthi
  • •Raise Nimbus EL inclusion in tracing tracking with BantagChase Wright

Agenda

From the call issue #2258Show

Agenda

Hive

Blocked Check-in

Key decisions

  • Error codes: positive values use new grouped catalog; negative values retain legacy semantics; no changes to simulate V1

    Positive error codes will use a new grouped catalog while negative codes remain legacy; simulate V1 unchanged.
  • Tracing API does not require an EIP; existing client implementations are sufficient

    No new EIP needed for the tracing API; current client implementations are adequate.

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.