EIP Editing Office Hour (EIP + ERC) Meeting #77, Oct 28, 2025

Agenda

Editor: @xinbenlv

To Final

To Last Call

To Review

Force merge

TBA

To Draft

Announcement

Meeting Time: Tuesday, October 28, 2025 at 16:00 UTC (60 minutes)

GitHub Issue

Meeting Summary:

The meeting focused on reviewing multiple Ethereum Improvement Proposals and ERC pull requests, with discussions centered around technical implementations and functionality details. The team examined specific proposals including an ERC20 pre-initialization extension with Sentinel storage and a bond system implementation, with detailed technical reviews and feedback provided by participants. The conversation ended with updates about an upcoming EIP Summit and the scheduling of the next review meeting.

Click to expand detailed summary

The meeting focused on reviewing and discussing Ethereum Improvement Proposals (EIPs) and ERC pull requests. Victor, the editor, joined to review proposals, starting with PR 1158 by German, who was present in the meeting. German’s proposal had been in the draft stage for some time and was ready for merging. Pooja mentioned that the proposal would be discussed once the editor was available. The meeting also addressed Rajat’s ongoing work on ERC-7518, which was still in progress and awaiting further review. The agenda for the meeting was shared, and participants were encouraged to share their PR links in the chat for review.

Zainan and German discussed a proposal for an ERC20 pre-initialization extension with Sentinel storage. German explained the implementation, which involves pre-loading storage with a magic value represented as a byte32 string to save gas. They explored how the system would handle token transfers and balances, with German clarifying that the magic value effectively disappears when performing arithmetic operations. Zainan requested to see a demonstration of the proposed system’s functionality, including a failure scenario, which German agreed to provide.

The team discussed a proposal review, with Zainan and Jon examining the technical aspects of an ERC implementation. Jon explained that the bond system works as a negative consequence for incorrect answers, with stakes being removed if agents provide wrong responses. The discussion focused on whether certain features could be optional, with Jon confirming that none of the core components could be omitted. Pooja mentioned that the author, John, was present for the review of PR number 1226, and the team agreed to prioritize the review once German completes certain transactions.

The meeting focused on reviewing and refining an ERC (Ethereum Request for Comment) proposal, with Zainan providing detailed feedback on various aspects of the document. Key points included clarifying the bond amount and implementation specifics, discussing judge selection methods, and addressing the need for more detailed specifications around the aggregation and resolution process. The group also touched on the use of different tokens for bonds and rewards, and the importance of providing clear guidance for implementers. German shared test results for a related proposal, which Zainan reviewed and approved. The conversation ended with Pooja announcing an upcoming EIP Summit at DevConnect and reminding participants of the next review meeting on November 4th.

Next Steps:

  • German: Execute four test transactions and post results in the Ethereum Magicians forum to demonstrate math works correctly
  • German: Address bot failures in the PR
  • Victor : Review German’s test transaction results once posted and complete the merge review for ERC-8003
  • John: Rephrase the bond definition sentence to separate the definition from implementation-specific details
  • John: Clarify whether deadline timestamp uses Unix epoch or block number, and declare if it’s implementation-specific
  • John: Include dispute process in the core flow overview section
  • John: Clarify what token the bond accepts and update the payable function documentation accordingly
  • John: Add bond token address to the request struct if allowing different tokens for bond and reward
  • John: Clarify what “must auto count” means using Solidity code demo
  • John: Clarify how to handle the case when Judge Agent believes Info agents need to be overwritten
  • John: Answer whether Judge Agent can override the majority of votes and clarify the aggregate function logic
  • Victor : Complete the remaining review of ERC-8033 in a future session
  • Rajat: Complete work on feedback for ERC-7518 and notify when ready for editor review

Recording Access:

YouTube Stream Links: