RPC Standards #025
Transcript
- Mercy Boma Naps-Nkari
- Simsonraj Easvarasakthi
- Mercy Boma Naps-Nkari
- Mercy Boma Naps-Nkari
- Chase Wright
I think we merge it and observe the behavior and then review it
- Mercy Boma Naps-Nkari
- Simsonraj Easvarasakthi
https://github.com/changesets/changesets would help
- Zane Starr
changesets or knope is another good one for that
- Mercy Boma Naps-Nkari
- Zane Starr
Reacted to "https://github.com/c..." with 💯
- Simsonraj Easvarasakthi
Reacted to "changesets or knope is another good one for that" with ➕
- Chase Wright
I did ask, nobody commented lol
- Mercy Boma Naps-Nkari
Reacted to "I did ask, nobody co..." with 😂
- Sina Mahmoodi
Reacted to "I did ask, nobody co..." with 😃
- Simsonraj Easvarasakthi
Reacted to "I did ask, nobody commented lol" with 😂
- Zane Starr
gotta drop thx folks
- Chase Wright
But you prune it in a window right?
- Mercy Boma Naps-Nkari
Reacted to "gotta drop thx folks" with ❤️
- Developer Uche
- Developer Uche
- Developer Uche
This right
Call summary
Decisions
- •TXPool namespace PR merged despite expected test failures due to non-deterministic behavior - 00:18:00
- •OpenRPC document version will track execution-apis release tags via CLI flag - 00:24:10
- •Engine API changes must be discussed on ACDE/ACDC, not RPC Standards calls - 00:47:45
Highlights
- Client Updates:
- ·Geth hasn't implemented standardized error codes yet; tests will warn only - 00:11:03
- ·TXPool content/status tests merged; will fail initially due to non-deterministic content - 00:18:00
- Organizational:
- ·Versioning approach: GitHub releases with pre-compiled artifacts, no caching issues - 00:19:15
- ·OpenRPC version will match execution-apis tag; added via CLI flag not YAML - 00:23:58
- ·Assembled spec branch used by Flashbots and downstream consumers - 00:31:41
- Testing Progress:
- ·Initial negative error code tests PR ready; includes replacement transaction underpriced - 00:06:12
- ·Test fixtures auto-generated; currently return Geth error codes with overrides - 00:08:20
- Critical Infrastructure:
- ·EF capabilities PR needs ACDE review; models client resource availability - 00:32:02
- ·Delete strategy field controversial; may make optional or rename to retention policy - 00:32:30
- ·Alternative: subscription-based availability notifications instead of static deletion strategy - 00:40:05
Action Items
- •Mercy or community contributor - Create Geth PR for standardized error codes implementation - 00:11:27
- •Mercy - Present EF capabilities PR (755) to ACDE for client team feedback - 00:38:07
- •All client teams - Review and comment on EF capabilities PR optional fields proposal - 00:41:03
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.