Meeting Summary:
The meeting focused on reviewing and discussing various pull requests (PRs) and issues related to Ethereum JSON-RPC standards, particularly around the Amsterdam update and the ETH simulate v1 specification. Chase explained that several PRs were blocked pending agreement on the simulate v1 spec, which needed updates like adding slot number and deprecating the transfer log. The group reviewed PRs related to log indexing, error codes, and method specifications, with input from client teams like Geth and Nethermind. There was uncertainty about how to proceed with the execution witness specification due to lack of engagement from consumers. The attendees also discussed issues with the Hive test framework and the need for schema validation changes. Chase agreed to merge some PRs that had consensus, such as removing an unused error code and clarifying certain payloads. The conversation ended with a reminder to create a meta-issue for the next release, which would follow the resolution of the Amsterdam update.
Click to expand detailed summary
Boma and Chase discussed starting a meeting, with Boma sharing her screen. Chase noted that it was a holiday in the US, which might result in low attendance. Marius asked if attendance had typically been high, to which Boma responded that it hadn’t been. The meeting appeared to be about to begin when the transcript ended.
Chase explained that progress on the current PR is blocked until the eSimulate V1 specification is finalized, which requires adding slot number, fixing the bell, and deprecating the transfer log. The team agreed on these specifications, and Chase mentioned that work is in progress to create a separate Amsterdam branch, though implementation details are still being worked out with Felix. Regarding PR 862, Chase indicated it is ready but depends on the Amsterdam changes being implemented first, and he approved the current version pending the Amsterdam updates.
Chase explained that the X55 PR needs updates to specify LogIndex following GoEthereum’s specifications and will need to be rebased on Amsterdam. Boma noted the need to track PRs blocked by Amsterdam to avoid conflicts. The discussion revealed that while Geth doesn’t require changes, Nethermind’s position on the logs index implementation remains unclear, as Łukasz indicated Nethermind doesn’t currently emit logs index.
Chase explained that Aragon and Reth need to update their log indexing from per-transaction to block-level to align with most other clients. He noted that a PR he submitted to GoEthereum has been approved and is pending Geth’s merge, after which the update can be merged. Chase also discussed challenges with specifying execution witness functionality due to disagreements among clients and ongoing spec work.
The team discussed challenges with specifying API requirements for zkVMs, with Marius expressing concerns about the significant changes in both consumers and producers of the API. Boma mentioned that Jason from the zkVM implementers had previously left comments, but there was uncertainty about whether to move forward with the specification or pause it. Chase noted that the lack of engagement from consumers was making it difficult to proceed, and the team considered bringing the discussion to a zkVM call for further input.
Chase and Łukasz discussed challenges with execution APIs, noting that different clients return varying results, making it difficult to determine what tests are effectively covering. Łukasz mentioned that some ZK-related tests exist but provided limited details about their scope. Boma inquired about the specific tests, and Łukasz indicated that Daniel and Ruben from his team had previously worked on them but had limited recollection of the details. Chase also highlighted that a Go Ethereum PR related to returning null for missing raw transactions has been pending review since June 26th, preventing further progress on the issue.
The team discussed unblocking several pull requests by removing an unused error code (-39001) from the blockchain. Chase explained that the error code change would unblock PRs for GetHeadersByHash and GetHeaderByBlockNumber, and while client teams should be notified of the changes, it likely wouldn’t affect them significantly since error codes are typically ignored. Marius agreed to review the PR, and Stavros indicated approval from the client team perspective.
The team discussed several PRs and specifications, with Chase presenting draft PRs for client fixes that need implementation across multiple clients. They agreed to proceed with specifying the methods after getting approval, with Chase planning to make the PRs non-draft after confirmation. The group reviewed a clarification for ETH simulate payload and agreed to merge it, while deciding to close a PR related to legacy data key behavior as it shouldn’t be part of the forward-looking schema. Łukasz and Chase provided detailed analysis of a getLogs improvement issue, explaining the limitations of current JSON RPC efficiency and discussing potential solutions including new endpoints with pagination capabilities.
The team discussed several pull requests and technical issues related to execution APIs. Chase explained a blocker in Hive testing that requires schema validation changes, which is currently pending review from client developers. The team agreed to merge a PR adding gas price tests after confirmation from Łukasz that it existed elsewhere. Chase committed to creating a meta-issue defining what should be included in an upcoming release, which is needed for DevNet testing, particularly for Layer 2 integration.
Next Steps:
- Chase: Update the PR for X55 to specify LogIndex according to GoEthereum and get agreement from other clients.
- Chase: Add a comment on the Go Ethereum PR (linked in PR 3,6) to request review as it is blocking progress.
- Chase: Get thumbs up from client teams on PR 779 (removing error code -39001) and then merge it.
- Chase: Move PR 777 out of draft and get client PRs merged once there is agreement on the spec for the methods.
- Chase: Merge PR 875 as all clients already implement the behavior.
- Chase: Merge the clarification PR for ETH simulate payload (block overrides) as no objections were raised.
- Chase: Close PR 872 as it’s about legacy behavior that should not be specified.
- Łukasz: Comment on issue 876 regarding the getLogs improvement suggestions.
- Chase: Double check and merge the PR adding tests for gas price (Amsterdam issue).
- Chase: Merge the PR adding tests for the object parameter in eth_call (CAID Overs).
- Chase: Create a meta-issue outlining what should be included in the next release.
- Chase: Fix the ETH simulate v1 spec in execution APIs, which is blocking other PRs (e.g., call tracer spec for Amsterdam).
Recording Access: