EIPIP Meeting 94

[poojaranjan]

Date and Time

Nov 15, 2023 at 15:30 UTC

Location

Zoom: TBA in the Discord #eip-editing channel

YouTube Live Stream/Recording: https://www.youtube.com/playlist?list=PL4cwHXAawZxpLrRIkDlBjDUUrGgF91pQw

Agenda

1. Discuss Open Issues/PRs, and other topics

• EIP-ERC repo split
  • Pending tasks for ERC migration
  • Migrating Pull Requests from ethereum/EIPs to ethereum/ERCs
• Web Page Rendering for EIP & ERC
• Topic Group
• EIP Editors & Associates based on repo split.

Call for Input

Call For Input	Status	Result	Comments
https://github.com/ethereum-cat-herders/EIPIP/issues/283	Open	-	Active for collecting responses (till Nov 16)
https://github.com/ethereum-cat-herders/EIPIP/issues/286	Open	-	Active for collecting responses (till Nov 19)
https://github.com/ethereum-cat-herders/EIPIP/issues/287	Open	-	Active for collecting responses (till Nov 19)
https://github.com/ethereum-cat-herders/EIPIP/issues/289	Deadline complete. 2 responses received in favor of withdrawing EIP-7199.	-	Active for collecting responses (till Nov 14)
https://github.com/ethereum-cat-herders/EIPIP/issues/293	Open	-	Active for collecting responses (till Dec 09)

• security-related EIP modifications Ref. comment and here

Changes to Final proposals

• Update ERC-223: Remove standard function ethereum/ERCs#49
• Update ERC-2612: ERC-2612 fix typo ethereum/ERCs#57
• Update ERC-1363: Fix created date. ethereum/ERCs#66 | Update ERC-1363: Move motivation and rationale to eip1 recommendation ethereum/ERCs#74 | Update ERC-1363: Remove external links and useless references ethereum/ERCs#75 | Update ERC-1363: Update specification natspec comments ethereum/ERCs#76
• update ERC1271 Ref comment @frangio
• Post EIP/ERC Split: Represent each side as Camps in Ethereum Magicians @NetWalker108
• Update ERC-1: Ethereum Request for Comments Process ethereum/ERCs#61 (Draft proposition for ERC-1) @Joachim-Lebrun

Manual Merge
TBA

2. Discussion continued or updates from past meetings

TBA

3. EIPs Insight - Monthly EIPs status reporting.

• Hackmd
• EIPsInsight.com

4. EIP Editing Office Hour

• Agenda Meeting 28 & Recording Meeting 27
• Rename it to ERC Office Hour?
• Can we merge All ERC Dev Meeting & EIP Editing Office Hour?

5. Review action items from earlier meetings

• Summary meeting 93

6. Announcement

ERC@Devconnect

[Dexaran]

I would like to add "security related EIP modifications" to the agenda. I wrote a draft for a proposal to update EIP process here: https://ethereum-magicians.org/t/modification-of-eip-process-to-account-for-security-treatments/16265/2

The idea is as follows:

• Make "Security Considerations" section of EIPs mutable even after the EIP is assigned final status. Security Considerations must be treated as "living".
• Develop an Ethereum Security Guideline (a new EIP that will describe security rules) so that EIP editors could benchmark proposals against it even without deep technical knowledge.

I have a security auditing organization (https://audits.callisto.network/), the necessary expertise in the area and a team that can work on the development of security guidelines. We would like to start the discussion and gather feedbacks.

[abcoathup]

• Make "Security Considerations" section of EIPs mutable even after the EIP is assigned final status. Security Considerations must be treated as "living".

I'd like Security Considerations & Implementations sections to link to a wiki post on Ethereum Magicians (https://meta.discourse.org/t/what-is-a-wiki-post/30801), similar to the link to Discussions. This enables these sections to be updated/maintained as appropriate by the community without changing final EIP/ERCs.

[abcoathup]

Is the "associate" role defined anywhere?
I can't make these meetings as they are incompatible with waking hours in Australia.

[poojaranjan]

@abcoathup

Editor Associate is not a formal position and is not listed on EIP-1.

This is added to indicate the user contributing to EIP/ERC reviewing and aspires to be an EIP Editor. This is also used as a tag on ECH Discord to add permissions.

A brief description of "who" and "roles" are added to an unofficial Reviewers sheet so it's helpful to keep track of.

[poojaranjan]

Summary

1. Discuss Open Issues/PRs, and other topics

EIP-ERC repo split

@Pandapip1 will be looking into tooling

Web Page Rendering for EIP & ERC

@Pandapip1 shared

• One website, but each repository will control how are the webpages rendered.
• Each working group gets to decide what should be displayed on the webpage.

Topic Group

@SamWilsn shared

• working on a prototype of how it should work
• 1 repo for each working group
• looks similar to EIP/ERC split
• will make sure of tooling working before the split
• will share and get editors' approval
• Check EIPs WG if anyone wants to follow along with working group development.

EIP Editors & Associates based on repo split.

@poojaranjan shared response added here

Call for Input

@SamWilsn shared

283

• Whoever voted are in favor
• Voting deadline ends tomorrow

286

• 2 votes in favor
• Responses accepted till Nov 19

287

• A lot on discussion thread
• preferred solution - moving in the reference implementations
• Responses accepted till Nov 19

289

• Deadline complete. 2 responses received in favor of withdrawing EIP-7199.
• Merging that PR

291

• Responses accepted till Nov 19

293

• Responses accepted till Dec 09

@Pandapip1 shared the idea of a shorter deadline for Call For Input for certain categories of issues.

• The decision could be reverted if people disagree.
• Maybe for changes that don't leave a side effect when reverted.
• @SamWilsn will give more thought and EIP-5069 can be updated as agreed upon.

security-related EIP modifications

• Vladimir Vencálek shared the issue and proposed solution.
• The proposal is summarized here
• Lot of discussion, watch the recording for details.
• No decision made. Open for continued discussion on FEM.

Changes to Final proposals

223

• @SamWilsn will merge it tomorrow, if nobody objects

57

• Merged

66

• Merged
• A bit of discussion on Created date, follow the recording, if interested.
• @Pandapip1 proposed an idea of allowing updating Final EIP for clarity of potential users.
• @SamWilsn isn't in favor and explained why "no"
• Could not reach any decision as we ran out of time.
• Will be included in the next meeting agenda.

EIPIP meeting 94 Chat.txt

Next meeting Nov 29, 2023 at 16:00 UTC

[poojaranjan]

Closing in favor of #297