EIPIP Meeting 113

[poojaranjan]

Meeting Info

• Date and Time: Feb 19, 2025 at 15:00 UTC
• Zoom shared on the ECH Discord #eip-editing channel
• EIPIP Meeting Recordings

Agenda

1. Discuss Open Issues/PRs, and other topics

Edit to Final Proposals

• Update ERC-6381: typo fix Update erc-6381.md ethereum/ERCs#866 (approved by author)
• Update ERC-7528: update required EIP for ETH (Native Asset) Address Convention ethereum/ERCs#870 (approved by author)
• Add proxy call to 6492 reference implementation ethereum/ERCs#878

Update to EIP-1

TBA

Other topics

• Stagnant Bot Issue: a tag to clarify an active consideration to prevent EIPs from being pulled in Stagnant Ref: Discord.

Call for Input

Call For Input	Status	Inclination/Result	Deadline
#373	Open	1, Favor	Jan 17, 2025
#374	Open	2, Favor	Jan 17, 2025
#376	Open	1, Opposed	Feb 6th, 2025

2. Other discussions and updates from past meetings

• EIP Reviewers- Where to document the list?
• Editor's Interest Survey report
• Adding new editors - PRs to update checklist & formalize process
  • EIP Editors' Workshop Summary

3. EIPs Insight - Monthly EIPs status reporting.

• February 2025
  • Editors & Reviewers leaderboard updates
  • EIP-Board updates
  • Pectra block countdown
  • Eipw integration to proposal builder
  • Eip-stagnant bot related queries
  • Monthly updates
• Website: Request to add our proposal builder tool link to eips.ethereum.org ethereum/EIPs#9244

4. EIP Editing Office Hour

• Agenda [51] Video [50]

5. Review action items from earlier meetings

• Notes 112

Next Meeting date & time - March 19, 2025 (3rd Wed of the Month) at 15:00 UTC

[viwinkumarpadala]

Hello @poojaranjan , I wanted to discuss few updates from EIPsInsight, and also discuss about few other things as well.

• Editors & Reviewers leaderboard updates
• EIP-Board updates
• Pectra block countdown
• Eipw integration to proposal builder
• Eip-stagnant bot related queries
• Monthly updates

[poojaranjan]

Meeting summary for EIPIP Meeting #113

Quick recap

The meeting covered various open PRs, community inputs. Discussions focused on reviewing and approving final proposals, addressing changes to existing proposals, and refining the process for managing Stagnant proposals. The participants also explored improvements to the EIP editing process, including the recent introduction of a reviewer program, updates to the EIPw Board, and plans for future meetings.

Next steps

• Sam to close the call for input on allowing links to blockchain Commons (issue #376) at end of day.
• Pooja to share the reviewer interest form report with the community.
• Pooja to add recommendations for new reviewers to join EIP meetings regularly and rotate as hosts for office hours.
• Pooja to initiate a conversation about moving EIP meeting agenda creation to ethereum/pm repository.
• Viwin to continue working on integrating more features like importing an EIP to the EIPsInsight website.
• EIP editors to review and respond to PR #9244 to add the new EIPsInsight website to eips.ethereum.org.
• Pooja to share GitHub handles of reviewer volunteers with the EIPs insight team for tracking progress.
 

Summary

Approving Minor Changes in Final PRs

• Matt & Pooja discussed two PRs for final ERCs: one for ERC-6381 and another for ERC-7528. Both PRs have been approved by their respective authors and contain minor changes. Approved by editors and will be merged.
• Matt and Sam approved merging these PRs, as they are for final proposals and the changes are small.
• Call For Input is created for the Add proxy call to 6492 reference implementation ethereum/ERCs#878

Proposal Changes and Network Upgrades

• Pooja brought up the topic to discuss the process of making changes to existing proposals for EIPs which are already deployed on the n/w upgrade. Would it require a new proposal or it could be updated?
• Sam initially agreed that small changes could be made to existing proposals without needing a new proposal, but larger changes, such as changing the gas cost of an opcode, would require a new proposal. Matt agreed as well.
• Pooja also mentioned a proposal to change a small spec for a future upgrade and asked if a new EIP would be needed or if the existing one could be updated.
• Sam clarified that if the change was already deployed on the network and a new fork wanted to change the behavior, it would be different. It would require a new proposal and will be added to a future upgrade with a small spec change.
• Pooja mentioned a possible spec change with the 'blob base fee' issue related to EIP-7706 when deployed. Sam clarified that if it hits the network, it needs a new EIP, and if not, it's fine not to.

Addressing Stagnant Bots

• Pooja then brought up the stagnant bot issue from the last meeting, which Viwin addressed. Viwin proposed a modification to the stagnant bot process, suggesting that if the EIP in consideration is included in the "Require" field of any Meta EIP, it shouldn't be moved to stagnant status. Sam agreed, suggesting that any active EIP could keep it out of stagnant status.
• Viwin also raised a question about changing the eip bot's code, which Sam suggested could be done by either branching off the old commit or using the new commit, provided it could be tested.
• Viwin discussed the status of the Last Call proposal, and Pooja raised a concern about proposals remaining in the last call stage indefinitely. Pooja suggested that authors should be prompted to move their proposals to the Final status.
• Sam agreed with this approach, suggesting that proposals should be moved to stagnant if they are past the last call deadline.
• Pooja agreed with this proposal as the bot only hits if the proposal has been inactive past six months.

Proposal Status and Call for Inputs

The team also discussed three call for inputs that had passed their deadline, with Sam providing updates on each. Sam decided to close one of the inputs at the end of the day.

EIP Reviewers and Editors Roles

• Pooja discussed the survey results of a recent EIP editors workshop, where 6 people expressed interest in becoming EIP reviewers.
• She suggested formalizing their roles and possibly promoting them to EIP editors after a 6-month review period.
• Sam proposed documenting these reviewers in EIP and granting them permission to merge up to the last call stage. He also suggested rotating them as hosts for office hours and encouraging them to attend EIP meetings regularly.
• Pooja agreed with these suggestions and planned to share the review report with the community, including the recommendations.

EIPw Bot Integration and Updates

• Viwin discussed the integration of the EIPw Board into EIPsInsight website website for easier accessibility and usability. He mentioned that they are working on importing an EIP and adding more features.
• The team also introduced a filter at EIP board for unnecessary labels and a slot countdown for Pectra upgrades on Sepolia and Holosky.
• On monthly insight,he reported that there were 3 EIPs, 3 ERCs, and one RIP added as draft , with 2 ERCs moved to the final state and 14 for Last Call EIPs.
• He also highlighted the addition of a 'last updated' feature for tracking updates.
• Pooja mentioned the usecase of the proposal builder tool and its potential for new authors. Viwin mentioned an open PR and the need for additional editors to finalize it.

Open questions

• Mercy asked about the reviewers, and Pooja clarified that it's a voluntary program. Pooja also discussed the reviewer program, emphasizing that it's an opt-in process rather than a selection.
• Viwin suggested providing GitHub handles for tracking progress.
• Pooja also proposed moving the agenda creation to the Ethereum PM for better visibility and participation.

The next meeting was scheduled for March 19th at 15:00 UTC

[poojaranjan]

Closed in favor of #382