All protocol calls
Previous
RPC2026-09-21_035

RPC Standards #035

2026-09-21 3 decisions 259 transcript lines

Transcript

Call summary

Decisions
  • •eSimulate V1 error-code categorization left unchanged; breaking changes deferred to eSimulate V2 - 00:02:14
Highlights
  • Error Codes:
    • ·Error-code standardization blocked on eSimulate V1 legacy codes; recommendation: leave V1 alone, address in eSimulate V2 - 00:02:14
    • ·Simsonraj will own error-code push; plans to DM Felix directly to drive Geth implementation - 00:04:41
  • V1 Release Blockers:
    • ·3-4 Geth PRs (thumbs-up'd but unmerged) are primary V1 release blockers; Chase pinged Marius and Felix - 00:07:10
    • ·V1 release chain: Geth PRs → fix eSimulate V1 → upgrade to Glamsterdam → V1 spec release - 00:16:27
    • ·Chase's Hive schema-validation PR likely superseded by Felix's more flexible Go-script approach (both WIP) - 00:10:24
  • Tracing Api Harmonization:
    • ·Issue #890: clients have significant trace-output differences; no agreed spec; Geth only supports debug namespace, not trace - 00:17:59
    • ·Geth unlikely to implement trace namespace until other clients converge on a unified spec - 00:20:45
    • ·Proposed approach: write spec, produce per-client diff table (as done for OpCode Tracer), then open alignment PRs - 00:23:44
    • ·No Trace V2 recommended; since no standard exists today, standardize in-place rather than versioning - 00:25:09
Action Items
  • •Simsonraj Easvarasakthi - Simsonraj to DM Felix and drive error-code standardization in Geth - 00:04:56
  • •Chase Wright - Chase to consult Mantec and begin trace-namespace spec draft with per-client diff table; not prioritized until V1 ships - 00:29:23

Key decisions

  • eSimulate V1 error-code categorization left unchanged; breaking changes deferred to eSimulate V2

    Error-code standardization was blocked on eSimulate V1 legacy codes; the group decided to address these in V2 to avoid breaking changes in V1.

  • V1 release chain: Geth PRs → fix eSimulate V1 → upgrade to Glamsterdam → V1 spec release

    Established the specific sequence of technical dependencies required for the V1 specification release.

  • No Trace V2 recommended; standardize in-place rather than versioning

    Since no official standard exists for tracing APIs today, the group decided to standardize the existing namespace rather than creating a new version.

Links

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.