EIPIP Meeting #128, July 08, 2026

Protocol Calls & happenings
3

Key Outcomes

The meeting addressed several editorial and process topics: shared resource duplication between EIP/ERC repos, Glamsterdam EIP status advancement, ETHBOT merge behavior fixes, EIPW rule enforcement, and inconsistencies in EIP-7723 (network upgrade inclusion stages). Editors agreed on key policy boundaries—no author-bypass merges for non-final EIPs—and identified multiple action items for Jochem and Sam. A brief demo of the EIP Lab tool was presented and deferred to the next meeting for a full walkthrough.

Decisions Made

  • Repo duplication fix: Use git submodules as the preferred short-term solution; Sam to write up an issue for community pickup.

  • Glamsterdam EIPs: Move all proposals to review status; editors to approve open PRs, author follow-up via ACD call.

  • DFI EIPs in Meta EIP: Declined-for-inclusion EIPs should be removed at review stage (not last call) to avoid blockers.

  • Non-final EIP merges: Editors must not merge without author approval except for obvious typos; policy to be formally documented in contributing.md or EIP-1.

  • External libraries in Solidity: Banned in the specification section; permitted in reference implementation sections.

  • RFC 2119 keywords: Only enforced inside the specification section; EIPW to flag keywords found outside it.

  • master → main branch rename: Rejected — would break downstream tooling with no meaningful benefit.

  • EIP-1 origin removal (PR #11845): Editors can approve directly; no special process required per EIP-5757.

Action Items

  • Sam: Update ETHBOT to include co-authors and PR number in squash commit messages.

  • Sam: Add EIPW issue for enforcing RFC 2119 keyword links (RFC 2119 / RFC 8174).

  • Sam: Review recently opened PR for copyright waiver enforcement.

  • Sam: Investigate EIPW rule for first-reference links not working in one repo.

  • Jochem: Create issues and action items from all ETHBOT/EIPW policy discussion points.

  • Pooja: Rebase PR #11883 (Glamsterdam); Sam will approve once rebased.

  • Pooja: Compile points on EIP-7723 inconsistencies (status vs. stage terminology, DFI handling, core-EIP-only scope) and add to next ACD agenda.

  • Pooja: Create a formal PR to document the editor merge policy for non-final EIPs.

  • EIP Lab team: Schedule full demo of EIP Lab tool for next meeting.

Pending Confirmation

  • EIP-7723 corrections: Two specific fixes needed — (1) replace “status” with “stage” throughout; (2) clarify DFI removal timing — pending author engagement and ACD discussion.

  • EIP-7723 scope clarification: Whether network upgrade inclusion stages apply only to core EIPs needs consensus before updating Meta EIPs (e.g., Fusaka, Glamsterdam).

  • EIP Working Group proposal: Pooja requests Sam’s review; currently scoped to 5 dispute types, may be reduced to 2–3.

Open Questions

  • Whether declined-for-inclusion EIPs should remain in Meta EIP history or be fully removed (git history as fallback reference was noted as acceptable).

  • Long-term repo unification: EIPSWG proposed as the eventual solution for EIP/ERC shared resources, but no timeline set.

Updates

  • EIP Working Group (Rito + Sam): First two foundational PRs merged, including repo manifest work; remaining PRs in review — community contributions welcome. 2

  • EIP Lab Demo (ariutokintumi + 0xoucan): Tool uses EVVM stack + AI agent to generate testable smart contracts for any EIP in ~3 clicks and under $5; demonstrated live with EIP-8034.

  • Next meeting: Targeting August 12th

  • August 4th office hour slot still open for volunteers. An available editor may add himself.