EIPIP Meeting 85

[poojaranjan]

Date and Time

July 12, 2023 at 14:00 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

• spam? Issue

Changes to Final proposals

• Update EIP-5169: Fix uncompilable memory in event ethereum/EIPs#7295
• Update EIP-6059: Clarify the backwards compatibility section ethereum/EIPs#7261
• Update EIP-2612: Make consistent indents in json ethereum/EIPs#7183

2. Discussion continued or updates from past meetings

• EIP-ERC GitHub repositories?
  Ref: Task list for ERC/EIP Split
• Update EIP-1: EIP pain relief ethereum/EIPs#7230

3. EIPs Insight - Monthly EIPs status reporting.

• Hackmd
• EIPsInsight.com

4. EIP Editing Office Hour

• Recording Meeting 21
• Agenda Meeting 22

5. Review action items from earlier meetings

• Summary

[xuxinlai2002]

Hello @poojaranjan , wanted to discuss ethereum/EIPs#7231, please consider adding this to review process.

[poojaranjan]

@xuxinlai2002 thanks for responding to editor's feedback. This PR isn't a good fit for this meeting. However, it can be discussed in EIP Editing Office Hour Meeting 22, if not merged in the next 2 weeks.

[poojaranjan]

Summary

1. Discuss Open Issues/PRs, and other topics

Changes to Final proposals

• PR-7295
• PR-7261
• PR-7183
  @SamWilsn will take a look and respond. Other editors will leave a comment (if any) on the PR thread.

2. Discussion continued or updates from past meetings

ethereum/EIPs#7230

• Long discussion. It will be better to follow the recording.
• Some of the editors were not in agreement with the proposed change to EIP-1 wrt EIP number allocation.
• As it was discussed, it looked like the PR needs to be split. @gcolvin agreed to split the PR and will be revisited in the next call.

EIP-ERC GitHub repositories? Ref: Task list for ERC/EIP Split

• Long discussion over the call. Revisiting the issue at recording
• EIP numbering: Not odd-even, but coordinated.
  • EIP Editors will allocate EIP numbers using a shared Google doc.
  • Most of the EIP editors agreed to the idea and showed a willingness to work together.
  • @lightclient will create a Google sheet and share it with the Editors.
  • Start with close to 100 as the first number of the new EIP number allocation

Progress on Bots

• EIPw: Keeping same config on the other repo, EIPw will work fine
• Eth-bot: Create a new repo, and have new secrets for that repository for eth-bot and it will work just fine.

[poojaranjan]

Closing in favor of #252

[poojaranjan]

Closing in favor of #252