EIPIP Meeting 96

[poojaranjan]

Date and Time

Dec 13, 2023 at 16:00 UTC

Location

Zoom: TBA in the Discord #eip-editing channel

YouTube Recording: EIPIP Meetings

Agenda

1. EIP Process Standardization

• [x] Updates on pending tasks for repo split
• [x] Web Page Rendering
• [x] Need a process for moving/cloning EIPs as RIPs and how they are numbered.

2. Discuss Open Issues/PRs, and other topics

• [x] https://github.com/ethereum/ERCs/pull/154
• [x] https://github.com/ethereum/EIPs/pull/7958
• [x] https://github.com/ethereum/EIPs/pull/7956
• [x] https://github.com/ethereum/EIPs/pull/8034

Call for Input

Call For Input	Status	Result	Comments
https://github.com/ethereum-cat-herders/EIPIP/issues/287	Open	-	Deadline completed on Nov 19, 2023
https://github.com/ethereum-cat-herders/EIPIP/issues/291	Open	-	1 Editor voted to oppose. Multiple other responses added. The deadline ended on November 30, 2023.
https://github.com/ethereum-cat-herders/EIPIP/issues/293	Open	-	2 Editors opposed to merging the PR. The deadline ended on Dec 09.

Changes to Final proposals

• [ ] https://github.com/ethereum/ERCs/pull/74 | https://github.com/ethereum/ERCs/pull/75 | https://github.com/ethereum/ERCs/pull/76
• [x] update ERC1271 Ref comment @frangio
• [ ] Post EIP/ERC Split: Represent each side as Camps in Ethereum Magicians @NetWalker108
• [ ] https://github.com/ethereum/ERCs/pull/61 (Draft proposition for ERC-1) @Joachim-Lebrun

3. Other discussions continued or updates from past meetings

Changes to Final EIPs

• Why Final EIPs are "Immutable"?
• Specify conditions under which Final EIPs can be updated.

4. EIPs Insight - Monthly EIPs status reporting.

• Hackmd
• EIPsInsight.com

5. EIP Editing Office Hour

• Agenda Meeting 30 & Recording Meeting 29

6. Review action items from earlier meetings

• Summary meeting 95

Next Meeting date & time

Jan 03 at 15:00 UTC?

[abcoathup]

Need a process for moving/cloning EIPs as RIPs and how they are numbered. EIP7212 has been moved or cloned (not clear on which yet) and whether it is best to keep the same number: https://github.com/ethereum/RIPs/pull/5/files#r1424823634

Can't attend the meeting as the time is incompatible with life in Australia.

[danceratopz]

If time permits, @smartprogrammer93 and I would be happy to discuss an idea to introduce a versioning scheme for Standards Track EIPs: https://github.com/ethereum/EIPs/pull/8034

[poojaranjan]

@abcoathup @danceratopz items added!

[poojaranjan]

Summary

1. EIP Process Standardization

Updates on https://github.com/ethereum/ERCs/issues/1

• PandaPip wasn't available. No updates were shared.

Web Page Rendering

• @SamWilsn has been working on webpage rendering
• Continued working on eth-review bot wrt working group-based rendering
• It's possible to have one domain to render all working group-based eips.

Need a process for moving/cloning EIPs as RIPs and how they are numbered.

• suggested by @abcoathup
• EIP-7212 has been moved to RIP repo. The question is whether to have the same or a new number.
• @SamWilsn mentioned that he supports having an L2 working group manage the process.
• @gcolvin mentioned that the group should have the freedom to decide on the process but it will be nice to have them part of the EIP-ERC numbering system to have unique EIP, ERC & RIP documentation.
• @poojaranjan and @gcolvin agreed that "Core" is not the best category as that enlists proposals for the Ethereum Mainnet deployment.

2. Discuss Open Issues/PRs, and other topics

• https://github.com/ethereum/ERCs/pull/154
• https://github.com/ethereum/EIPs/pull/7958
• https://github.com/ethereum/EIPs/pull/7956 @SamWilsn will take a look at these PRs. Ahmad shared the concern of external contributors making typo edits to maybe participate in airdrops. Sam finds genuine PR with meaningful changes to be merged even if it is a typo fix. But, doing format and minor changes just to get a commit in will have least chances of getting merged.

https://github.com/ethereum/EIPs/pull/8034

• Danceratopz and Ahmad Bitar introduced this new proposal.
• Major, minor, patch versioning
• It will be helpful for testing team and other following the breaking changes of the specification.
• Closely tied to EIP status, helpful for implementation
• Changelog has to be added for tooling but EIP editors has to be more attentive.
• It can be author provided.
• It can not go retroactively update older EIPs but for future EIPs only.
• @SamWilsn with questions helped us understand the proposal even better, worth following the discussion
• Overall people on the call considered to be a good proposal.
• Victor (ERC editor) shared generally positive feeling and follow the implementation on EIPs side to be considered on the ERC side as well.

Call For Input

287

@SamWilsn doesn’t feel comfortable without consulting other Editors on the call. Victor: Leave them as is Greg: Moved Matt: Delete (but mostly indifferent) @SamWilsn will update and close the Call for Input

291

• Editors may add comments
• Will be closed by EOD today

293

• Editors may add comments
• Will be closed by EOD today

Changes to Final proposals

Update 1271

• Howey
• Found some weird edge case with 1271
• Hoping to have the disclosure process to update the proposal @SamWilsn thinks it is good venue to talk about Security vulnerability in general

In response to do we want to update a Final EIP with “Security vulnerability”

• Matt: Probably not
• Victor: Yes, but depends on case by case
• Greg: no opinion

@poojaranjan suggested to have Call For Input to have conditions specified under which a “Final” proposal can be updated

Next Meeting date & time - Jan 03 at 15:00 UTC

[poojaranjan]

Closing in favor of #302

[vittominacori]

Hello @poojaranjan, any update about these PRs?

• Update ERC-1363: Move motivation and rationale to eip1 recommendation
• Update ERC-1363: Remove external links and useless references
• Update ERC-1363: Update specification natspec comments

[poojaranjan]

Added to the next agenda!