EIP Improvement Process

EIPIP Meeting #131 confirmed the EIP Coordinator role as distinct from associate editors and nominated Pooja as the first coordinator (call for input open until Nov 4). Editors agreed a discretionary merge policy for typo/formatting fixes on active, non-final EIPs, closed Calls-for-Input 409 and 413, and will merge EIP-5069 once conflicts are resolved. Sam is stepping down as Keeper of Consensus, with a successor vote added to the next agenda; Justin is onboarding as an editor starting with CL-related reviews. The team is moving toward AI tooling to help authors and editors follow EIP/ERC rules, and flagged a shortage of ERC reviewers. 24 proposals reached Last Call in the past month as Glamsterdam EIPs moved to testnet.

EIPIP #130 worked through the open Calls for Input, tightened the editorial process, and heard an EIPsInsight demo. Editors agreed to merge the Unicode Technical Standards and 'Add Associate EIP Editors' CFIs, backed creating an EIP Coordinator role for the social and mentoring side of the process (distinct from associate editors and without number-allocation rights, pending Victor's final comment), decided to keep Calls for Input in the current EIPIP repository rather than moving them to ethereum/EIPs, and integrated contributing.md updates on EIP numbering and a no-force-merge, two-editor-approval policy for active EIP PRs. The group also flagged the lack of dedicated tooling engineering, including the stagnant bot not running on the ERC repository, as a growing risk.

EIPIP #129 debated a proposed strict rule for changing an EIP's author list, agreed that authors must not self-allocate EIP numbers, and worked through why the Glamsterdam meta EIP is stuck in Draft. Editors decided to document number allocation as an editor responsibility (in contributing.md, the template, and the EIPW message), leaned against a hard author-removal rule in favor of an objection period, and agreed to raise the meta EIP's out-of-status references and an undocumented mascot addition at ACD. The EIP working-group Rust rewrite is at risk of being dropped without more editor buy-in.

EIPIP #128 focused on getting the Glamsterdam EIPs into Review, tightening editorial tooling rules, and clarifying editor merge discretion. Editors agreed to keep shared EIP/ERC files in sync via a git submodule, to have ETHbot preserve authors and PR numbers in merge commits, to disallow external Solidity imports in the Specification section (but allow them in Reference Implementation), and to enforce RFC-2119 keywords only in the Specification section. They also set a policy: editors may merge author-stale PRs only for Final EIPs, not non-final ones, and discussed fixing EIP-7723's status-vs-stage confusion via ACD.

EIPIP #127 closed the external-resources call for input (OWASP/CT-PA/CAI are licensed for republishing under the EIP-5757 process) and agreed to write a call for input to create a proper authorship-change policy, since none exists today. Editors agreed to keep oldest-waiting-first as the default review order while allowing PRs linked on the ACD agenda to be prioritized neutrally, debated Pooja's proposed dispute-resolution working group, and celebrated ERC-4337 being merged as Final at the 100th office hour.

EIPIP #126 closed several long-open calls for input, agreeing to render each EIP's real status in its citation (instead of always 'draft'), to treat Final rather than Living as the default end status for most proposals, and to keep allowing Solidity in proposals provided the version is stated. Editors set guidance on pre-final CAIP dependencies and on using AI as an editorial tool, discussed making office hours a feedback venue rather than a review fast-track, and worked through community dispute-resolution cases. RTO demoed the V2 next-generation EIP tooling (local multi-repo build system, Pagefind search, and a hard-fork index).

EIPIP #125 worked through the passed call-for-input items (Unicode technical standards, the associate-editor role, and citation formatting), then debated whether citations should carry a 'draft' marker and whether the EIP-7870 hardware-requirements proposal should stay Living or move to Final. Editors agreed to merge Greg's static-control-flow write-up as an Informational EIP, confirmed progress on an automated EIP-numbering bot, and heard a community demo of a multi-repo local build system for the next-generation EIP website.

EIPIP #124 agreed to add a new associate-editor tier, reaffirmed that most proposals should default to Final with Living reserved for editor-authored governance documents, and tackled the flood of ETHbot GitHub mentions that ping every editor on every PR. Editors decided to stop @-mentioning all editors from the bot (replacing it with a non-pinging note), agreed AI agents may assist with low-hanging reviews and labeling but not close or merge PRs, and heard an EIP Insight demo of a new process-type PR board and contributor-analysis pages.