RPC Standards # 6 | June 9th

[jflo]

RPC Standards # 5 | June 9th, 2025

• June 9, 2025, 15:00 UTC

Agenda

• demo: docusaurus vs. gatsby
• divorcing structure from data: the role of JSON schema in testing spec compliance. rpc-compat tests should just validate against a schema. dependency on underlying data should be minimized or eliminated.

Styleguide

• guidelines on error handling; get the code right, get the message helpful and accurate
• Empty search results: 200/null , 200/[], or -3200: Not Found?
• Ordering of error reporting - specifying error reporting often impacts logic flow from clients.

PRs

• Adding timestamps to log receipts
• Error Codes - Standardize JSON-RPC Error codes execution-apis#658

The zoom link will be sent to the facilitator via email
Facilitator emails: justin@florentine.us

🤖 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

[github-actions]

• Action: Bot processing finished at 2025-05-28 16:38 UTC

Discourse Topic: Title already exists.

• ⚠️ Could not find existing topic ID in mapping for this duplicate title.

⚠️ Error: Missing or invalid date/time format. Found potential date/time fragments: June 9, 2025 15:00 UTC Please correct the format in the issue body.

Calendar Event: Skipped creation due to missing time/duration in issue.

• Zoom Meeting ID invalid or missing, skipping email notification.

Telegram Notification

• Sent message for this occurrence to Ethereum Protocol Updates channel

[acolytec3]

This draft PR will update the docs to use the new OpenRPC v2 generator tooling and would bring gatsby back. Would be happy to discuss further on tomorrow's call.

[poojaranjan]

Recording: https://youtu.be/q0xp29LoMCs