RPC2026-04-06_024
RPC Standards #024
2026-04-06 2 decisions 449 transcript lines
Transcript
At a glance
TxPoolInspect excluded from spec due to non-testable client-specific strings
TxPool tests remain spec-only until custom validation framework implemented
Detailed notes
Testing Updates
- •Error message checking fix merged for RPC compatibility testing00:03:30
- •Testing buildBlockV1 merged; most clients now support it00:10:50
- •getStorageValues method added to spec; supported by Nethermind, Reth, Geth00:11:14
Legacy Compatibility
- •Receipt post-state root field remains only protocol-breaking API change mid-chain00:40:00
- •Profiles would require separate chain RLP files per profile configuration00:51:27
Txpool Specification
- •TxPool methods under review; TxPoolInspect to be excluded (non-standardizable)00:12:22
- •TxPool testing requires framework enhancements for custom validation logic00:14:17
Versioning And Profiles
- •Docs site versioning PR adds dropdown but requires release pipeline work00:22:00
- •GitHub action must fetch OpenRPC JSON from releases to build versioned docs00:26:00
- •Post-merge-only client support blocked on profiles feature implementation00:37:21
Action items
- •Remove TxPoolInspect method from specification PRMercy
- •Create profiles feature issue and link post-merge support dependencyFelix/Chase
- •Invite Ethrex team to future RPC Standards callsChase
Agenda
From the call issue #2001ShowHide
Key decisions
TxPoolInspect excluded from spec due to non-testable client-specific strings
TxPoolInspect method excluded from specification PR due to non-testable client-specific stringsTxPool tests remain spec-only until custom validation framework implemented
TxPool tests will remain spec-only until a custom validation framework is implemented
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.