EIP Improvement Process #130

Summary

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.

Decisions

• •Merge the Unicode Technical Standards CFIs: one is already merged, and Sam will force-merge the second after resolving conflicts.
• •Approve and merge the 'Add Associate EIP Editors' CFI; it is past the deadline and closing is affirmed.
• •Support creating an EIP Coordinator role for the social and mentoring side of the process, distinct from associate editors and without number-allocation rights; the final decision is pending Victor's comment (deadline Sep 26).
• •Keep Calls for Input in the current EIPIP repository rather than moving them to ethereum/EIPs or duplicating them, to avoid fracturing the EIP and ERC process.
• •Integrate the contributing.md updates: EIP numbering guidance and a policy that active EIP PRs are not force-merged and require two editor approvals.

Highlights

• •Unicode Technical Standards CFI: one PR is merged; Sam will force-merge the second after resolving conflicts (it already has enough approvals).
• •Add Associate EIP Editors CFI: past the deadline and closing affirmed, approved for merge; editors who did not respond are dropped per the process.
• •EIP Coordinator CFI: general support for a social and recognition role that guides authors, sits alongside associate editors, and cannot allocate EIP numbers; the deadline is Sep 26 and a final decision waits on Victor's comment. lightclient (Matt) was skeptical that a new title helps.
• •Strict rules for changing authors (CFI 409): still gathering editor responses (Sam opposed, one in favor); a friendly ping will go out to editors.
• •Calls for Input will stay in the current EIPIP repository rather than move to ethereum/EIPs or be duplicated, to avoid fracturing the EIP and ERC process; Gajinder noted EIPIP predates and is not dependent on the Ethereum Cat Herders entity.
• •contributing.md was updated with EIP numbering guidance and a policy that active EIP PRs are not force-merged and require two editor approvals.
• •The stagnant bot does not run on the ERC repository and needs to; a community PR (from Cyber Sentry) awaits review, and there is no dedicated engineering support for EIP tooling.
• •A stagnant EIP reference was flagged: the FOSM/FOCIL EIP references EIP-7547, which is now stagnant; the re-enabled reference-status check should surface this on the next PR or review.
• •Status upgrade checklist: Pooja shared a first pass separating author and editor responsibilities per status; Gajinder proposed a bot auto-post the checklist as a PR comment (editable by editors), with an AI bot filling it in as a later step.
• •Devcon: the EIPIP Hub was selected as one of 14 hubs (out of about 33 applications) with over 160 confirmed attendees.
• •EIPsInsight demo: EIPIP meeting notes (recording, AI summary, key decisions, searchable transcript), the consolidated Office Hours hub (PR board, analytics, calls archive, an ACD-agenda tab and CI-blocked PRs), and a new Account Abstraction page tracking EIP-7702 and ERC-4337 on-chain usage and value plus the working-group calls.
• •Neutrality concern: Jochem cautioned that featuring popular proposals such as Account Abstraction under 'Featured Hubs' could make EIPsInsight look less neutral, and suggested a separate site for that content.

Action Items

• •Sam - Force-merge the second Unicode Technical Standards PR after fixing conflicts, and review and comment on the stagnant-bot (Cyber Sentry) PR and the EIP Coordinator CFI after the call
• •Editors - Review the first-pass status-upgrade checklist and add comments, and add responses to the strict-author-change CFI (409)
• •Jochem - Open a PR (agents.md) instructing LLMs not to allocate EIP numbers in drafts
• •Dhanush / EIPsInsight - Investigate a filter to distinguish PRs waiting on editors versus waiting on authors (PR author vs EIP author), possibly via a bot-flagged comment
• •Pooja - Follow up on securing engineering support for EIP tooling, continue the EIP Coordinator discussion async, and finalize the next meeting date in Discord