RPC2026-08-10_032

RPC Standards #032

2026-08-10 2 decisions 231 transcript lines

Transcript

At a glance

Merge execution-apis Get Subscribe PR (previously blocked by upgrade); Chase Wright to merge
HiveChain upgrade to Glamsterdam identified as primary blocker; unblocking it is the immediate priority

Detailed notes

Error Codes

  • •Error codes work stalled: Felix OOO, Sina no longer attending; no public forum discussion ongoing; blocked 1+ year00:22:01

Execution Apis Prs

  • •execution-apis#859 (EIP-1898 additional tests): ready to merge pending broader thumbs-up in Discord00:11:57
  • •execution-apis#858 (duplicate test cleanup + fixture regen): ready to merge pending additional review00:15:51
  • •BAL-related execution-apis PR on hold; 2 open client issues referencing it need resolution first00:20:34

Hivechain Blockers

  • •HiveChain not yet on Glamsterdam; blocks majority of execution-apis testing and PRs00:07:17
  • •HiveChain needs regeneration with Glamsterdam-compatible chain before draft tracking PR (hive#1589) can be rebased and tested00:09:33
  • •Geth not honoring target gas limit in engine API (hive#862); PRs opened in go-ethereum, ethrex, and Reth to patch00:17:07

Action items

  • •Review and merge hive#1587 and hive#1588 today to unblock Glamsterdam HiveChain worklightclient
  • •Post release/error-codes status to Discord and flag for Felix on returnBoma

Agenda

From the call issue #2185Show

Agenda

Hive

We need this merged

Carried over from last call

Error codes & release

  • Do we proceed with Chase's PR as-is and keep error codes separate (per Simsonraj's suggestion last call), or wait for the error codes discussion to resolve (823 / 784)?
  • Can we cut v1.0.0-beta.8? Last release was June 10 - do error codes block it, or do they land in a later release?

Key decisions

  • Merge execution-apis Get Subscribe PR (previously blocked by upgrade); Chase Wright to merge

    unblocking previously blocked PR
  • HiveChain upgrade to Glamsterdam identified as primary blocker; unblocking it is the immediate priority

    identifying the immediate priority

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.