Meeting Summary:
The meeting focused on reviewing pending pull requests (PRs) for the execution API and discussing implementation challenges. Boma led the discussion by sharing screen and reviewing various PRs, including a debug execution witness issue that needed input from the zkVM team. Chase explained that he had only drafted the YAML standard portion and requested input from the zkVM team, particularly Kevaundray, who agreed to review the issue and send it to relevant team members for feedback. The team discussed versioning challenges for the API, with Chase noting that JSONRPC hasn’t handled versioning well historically and options include prefixing with “v1” or dealing with it through releases. Several PRs were discussed including PR 801 which Chase needed to review further due to recent comments, and PR 851 which required testing and proper .io files for BAO implementation. The team decided to drop some PRs from future calls and address them later, particularly ones involving Hive support that required more EVM expertise. The conversation ended with Simsonraj raising concerns about error codes implementation, noting that discussions were still ongoing with Sina and Felix, and suggesting they might proceed with Chase’s PR while keeping error codes separate for future versioning.
Click to expand detailed summary
Boma and Chase discussed reviewing pending pull requests, noting that most were old and not sure about the preferred order. They confirmed that Felix was not attending the meeting. Boma mentioned a debug execution witness issue from September and asked if they should wait for the zkVM team to address it.
Chase explained that he only drafted the YAML standard portion of the API and made the keys field optional based on Tulio’s request, but he is not driving the implementation. Boma suggested taking the proposal to ACDE for review, and Chase agreed to this approach. Stavros suggested bringing it up on a zkVM call, though it was unclear if such calls exist.
Kevaundray informed the team about an upcoming zkVM monthly call scheduled for two weeks later. Boma presented an issue regarding debug execution witness where different clients have implemented varying solutions, and requested the team to review and comment on what should be specified and how clients should implement it. Kevaundray confirmed they have specs and execution tests in place for this issue and agreed to review the repository link shared by Boma, though they raised a question about versioning implementation that remained unresolved at the end of the discussion.
Chase discussed the challenges with versioning in JSONRPC and presented three potential solutions: adding a “v1” prefix to the API, retroactively updating methods without prefixes, or incorporating versioning information in response bodies. Kevaundray noted that versioning issues also affect EF get proofs, which are linked to the current state tree. Boma expressed uncertainty about the best approach to handle versioning and mentioned that this topic was previously pushed forward by Kyra.
The team discussed PR 801, but Chase indicated they couldn’t merge it yet due to pending feedback on a superseded PR 787. Chase mentioned there were comments and questions in Discord about testing build block functionality that needed review. The team agreed to backlog PR 801 for the week and address the outstanding feedback first.
Boma and Chase discussed issues with .io files and BAO implementation, noting that the first PR was merged without the necessary files. Chase mentioned that Glamsterdam support is not yet available in HiveChain, preventing testing of bells.
The team discussed approving item 851, with Chase indicating he needed to test it and would do so today. Boma mentioned that Terrence had been tagged to review it, but there were pending comments from Felix that needed addressing. The group determined that Carrie should not be tagged for updates since she is no longer working on RPC standards, and they considered whether to create a new PR or drop the item from future discussions.
Chase proposed dropping a two-dimensional gas tracing project for now due to its connection with Glamsterdam and the need for Hive support. Boma suggested involving Felix or someone with more EVM experience to review the semi-vibe-coded PRs, and Lightclient indicated they would need to examine the details before commenting further. The discussion highlighted uncertainty about what is currently blocking the implementation of a specific PR, despite another blocking PR having been merged earlier.
The team discussed merging the e-subscribe feature without tests, with Chase indicating this approach would not be unprecedented. Boma confirmed no one had strong opinions on the matter, and the group concluded they could proceed with merging the spec file without immediate testing. The conversation ended with no additional agenda items or concerns raised about the Ejection API release process.
The team discussed updates on error codes, but key participants Sina and Felix were not available to provide updates. Simsonraj suggested moving forward with Chase’s PR with minor modifications to keep concerns separate rather than waiting for error codes v2. Simsonraj agreed to follow up in a Discord thread to get more information and potentially schedule a breakout call when everyone is available.
Next Steps:
- Boma: Bring up the debug execution witness issue to ACDE for review and input.
- Kevaundray: Review the debug execution witness PR and share it with the zkVM team for feedback.
- Chase: Review the feedback and questions on PR 787 and address them before proceeding with PR 801.
- Chase: Test PR 851 and provide feedback.
- lightclient: Look into the Hive PRs related to the Call Tracer and two-dimensional gas tracing.
- Simsonraj: Follow up on the error codes discussion thread on Discord and try to get responses from Felix and Sina.
Recording Access: