RPC2026-04-06_024
RPC Standards #024
2026-04-06 2 decisions 449 transcript lines
Transcript
Call summary
Decisions
- •TxPoolInspect excluded from spec due to non-testable client-specific strings - 00:13:27
- •TxPool tests remain spec-only until custom validation framework implemented - 00:20:40
Highlights
- Testing Updates:
- ·Error message checking fix merged for RPC compatibility testing - 00:03:30
- ·Testing buildBlockV1 merged; most clients now support it - 00:10:50
- ·getStorageValues method added to spec; supported by Nethermind, Reth, Geth - 00:11:14
- Legacy Compatibility:
- ·Receipt post-state root field remains only protocol-breaking API change mid-chain - 00:40:00
- ·Profiles would require separate chain RLP files per profile configuration - 00: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 logic - 00:14:17
- Versioning And Profiles:
- ·Docs site versioning PR adds dropdown but requires release pipeline work - 00:22:00
- ·GitHub action must fetch OpenRPC JSON from releases to build versioned docs - 00:26:00
- ·Post-merge-only client support blocked on profiles feature implementation - 00:37:21
Action Items
- •Mercy - Remove TxPoolInspect method from specification PR - 00:14:17
- •Felix/Chase - Create profiles feature issue and link post-merge support dependency - 00:54:00
- •Chase - Invite Ethrex team to future RPC Standards calls - 00:57:12
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.