Open Issues:
Open PR’s:
Meeting Time: Monday, January 26, 2026 at 15:00 UTC (60 minutes)
The team discussed the migration of the RPC test generator to a new repository and addressed various technical issues related to testing and linter problems. They reviewed ongoing PRs and discussed versioning schemes for Execution API and JSON RPC endpoints, with specific attention to backward compatibility concerns. The conversation ended with discussions about improving website content readability and addressing bugs in the spec, including plans to seek input from the Geth team regarding test implementation challenges.
Mercy led a meeting about RPC Standard Core 19 on January 26, 2026, but Patcha was not present. Chase explained that the RPC test generator, which creates .I/O files for Hive test chain, is being moved from the Lightclients repo to the Ethereum-owned repo. Mercy requested clarification on how to import .I/O files and proceed with future PRs, and Chase clarified that the process would not be significantly different from the current workflow.
Mercy and Chase discussed the process of running commands to clone repositories and generate tests, clarifying that the same command would be executed from within the execution APIs to automatically regenerate tests. Mercy inquired about merging rights for a specific pull request, which Chase confirmed was merged, while another PR (number 733) remained open to address CI and linter issues. The team also discussed website changes, with Chase suggesting that the example generator on the right side of the screen should be made more accessible or hidden to improve content readability, and Zane acknowledged the request, agreeing to investigate further.
Zane identified bugs in the spec, particularly with EFSimulate not following JSON schema, and mentioned that the OpenRPC team is working on a linter to address these issues. Chase discussed formatting confusion in the parameters section, noting that the line breaks and requirements (AND/OR) were unclear. They also talked about the successful merge of the RPC test generator into the Execution APIs repo, which introduced some linter and CI failures, and a PR was created for review and merging.
Mercy raised concerns about missing tests for some methods in the execution-apis repository and created an issue to address this. Chase explained that writing tests for methods with filters would be challenging due to nondeterministic filter IDs returned by clients. They discussed the need to fix a linter issue before proceeding with certain changes, but Chase suggested working on related tasks in parallel. Mercy requested Chase’s help in getting more clients to review and merge a specific PR, and Chase agreed to reach out to relevant team members.
Mercy and Chase discussed the need for stricter field value options in the “Get transaction by hash” feature to simplify testing, with Chase encouraging FLCL to leave a comment on the issue. Simsonraj reported limited progress on error code standardization and the hype test, suggesting merging the original PR since it doesn’t affect validations or generations, pending team agreement.
Mercy and Simsonraj discussed a blocking lint issue in the repository that needs to be fixed before they can manage PRs and continue with core developers. Simsonraj mentioned the need to write tests and get them approved before implementation, but noted challenges with the current test generator due to Geth’s lack of support for certain error codes. They agreed to seek input from the Geth team on whether to write custom tests or wait for Geth’s implementation, with Simsonraj planning to share details in the AllCoreDevs channel and potentially involve Felix from the Geth team in the next meeting.
Mercy and Chase discussed the process of versioning specs and creating a release. They agreed to go through current PRs and issues to determine what features should be included in the first version. Mercy suggested creating a list and posting it in the chat for collective input. Zane mentioned that line breaks would be an easy fix, but the interactive widget might require more thought.
The team discussed versioning schemes for Execution API and JSON RPC endpoints, with Tullio proposing both repository versioning and endpoint versioning. Mercy raised concerns about getting input from application users, suggesting they might reach out to Sam for feedback. Chase noted that adding versioning likely wouldn’t break backward compatibility since everything currently pulls from main. Zane mentioned a PR for restoring built assets in the spec repo, which Mercy agreed to follow up on.
B%7yzGpY)B%7yzGpY)B%7yzGpY)YouTube Stream Links: