RPC2026-10-05_036
RPC Standards #036
2026-10-05 2 decisions 161 transcript lines
Transcript
- Łukasz Rozmej
I barely hear you @Boma
- Chase Wright
Sorry I was battling a giant bug in my house lol
- Boma
Reacted to "Sorry I was battling a giant bug in my house lol" with 😂
- Boma
- Simsonraj Easvarasakthi
- Simsonraj Easvarasakthi
Reacted to "Sorry I was battling a giant bug in my house lol" with 😂
- Łukasz Rozmej
Decouple from Geth!
- Ahmad Wilson
Reacted to Sorry I was battling... with "😂"
- danceratopz
Reacted to "Decouple from Geth!" with 👀
Call summary
Decisions
- •Error codes: positive values use new grouped catalog; negative values retain legacy semantics; no changes to simulate V1 - 00:17:37
- •Tracing API does not require an EIP; existing client implementations are sufficient - 00:23:34
Highlights
- 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 V1 - 00:17:37
- Tracing Apis:
- ·Tracing spec blocked on Geth PRs; Bantag has draft Geth PR but won't finalize until all clients agree - 00:20:07
- ·Felix's validation script PRs (execution-apis + Hive) are 99% done; minor feedback outstanding before merge - 00:26:49
- ·Nimbus EL not tracked in tracing compatibility work; Chase to follow up with Bantag - 00:29:04
Action Items
- •Simsonraj Easvarasakthi - Open PR for unified error code catalog; positive = new grouped, negative = legacy - 00:19:34
- •Chase Wright - Raise Nimbus EL inclusion in tracing tracking with Bantag - 00:29:06
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.