RPC Standards #7 | June 23rd, 2025 #1585
Description
RPC Standards # 7 | June 23rd, 2025
- June 23, 2025, 15:00 UTC
Agenda
- Decision: docusaurus vs. gatsby - OpenRPC suggests using gatsby, will be more future-compatible with their roadmap.
- Discussion: validating structure, not data values
- specs are currently disconnected from tests: feature or bug?
- adding json schema validation for requests to rpc-compat tests
- How are bugs in requests found today? We compare the spec to Geths implementation to determine which is at fault.
- Devs cannot test their requests without updating Geth. Feature or Bug?
- Necessary if we want to cover API inputs prior to sending them to a client.
- Proposed action: Add json schemas to cover requests
- Discussion: can these be derived from the yaml schemas?
- Complication: where do they get executed?
- build time validator of .io files against a json schema?
- Do we need to add a schema validation layer to rpc-compat in hive?
Styleguide
- Empty search results: 200/null , 200/[], or -3200: Not Found?
- best way to find these inconsistencies across the spec and start to align them?
- Ordering of error reporting - specifying error reporting often impacts logic flow from clients.
PRs
- Adding timestamps to log receipts
- what is keeping us from merging this?
- Geth has already adopted it? eth/filters: add timestamp to derived logs go-ethereum#31887
- Error Codes - Standardize JSON-RPC Error codes execution-apis#658
- Proposed next actions?
- Adopting this doesn't seem to help us get rid of error message translation.
- Proposed next actions?
The zoom link will be sent to the facilitator via email
Facilitator emails: [email protected]
🤖 config
- Duration in minutes : 60
- Recurring meeting : true
- Call series : API
- Occurrence rate : bi-weekly
- Already a Zoom meeting ID : false
- Already on Ethereum Calendar : false
- Need YouTube stream links : false
- display zoom link in invite : true