EIPIP Meeting #132
Transcript
Call summary
Key Outcomes
- •AI-assisted EIP reviews will be piloted as a read-only process to help editors manage high proposal volume without auto-merging.
- •EIP Builder was demonstrated for drafting, validating, and reviewing EIPs, with potential for integration into the official EIP site.
- •Exceptional PR merging by editors was rejected to maintain neutrality and author responsibility.
- •The Keeper of Consensus election remains open for 30 days due to quorum rules.
Decisions
- •AI Review Pilot: Start with a read-only AI bot that posts reviews as comments; no auto-merging of PRs.
- •AI Scope: Focus on structural and formal checks (backward references, abbreviations, copyright, RFC 2119 keywords) rather than changing original ideas.
- •Exceptional Merging: Editors will not merge PRs without author approval, even for clearly factual corrections like the postponed Hoodi activation date on EIP-7773; it stays the authors' responsibility.
- •EIP Builder Integration: Open to hosting the EIP Builder on eips.ethereum.org if it can be self-contained and client-side, pending discussion with Matt.
Progress & Status
- •AI Review Bot: Currently in a hybrid mode where Jochem reviews AI-generated comments before posting.
- •EIP Builder: Validates against EIP-1, the EIP template, and eipw lint; can import existing EIPs and PRs and suggest RFC 2119 boilerplate.
- •PR Backlog: Over 550 open PRs; many are waiting on authors or are design updates to EIPs not opened by the original authors.
- •Stagnant Bot: Change request reviewed by Sam; pending Jochem's final check.
- •EIP-1 Update: PR 12643 to add the EIP coordinator's name is pending editor approval.
Risks & Blockers
- •AI Feedback Loop: Risk that AI-generated EIPs reviewed by AI could drift from the original author's intent.
- •False Positives: AI reviews may produce incorrect comments, increasing author workload.
- •Neutrality: Promoting external tools on the EIP repository could compromise perceived neutrality.
- •Editor Capacity: High volume of complex EIPs makes manual review difficult; some editors have limited availability.
Open Questions
- •AI Review Triggers: Whether the bot should re-review after every commit or use a manual trigger or delay.
- •PR Limits: Whether to limit the number of open PRs per contributor (currently viewed as inappropriate for an open ecosystem).
- •Keeper of Consensus: Who will take over the role after Sam steps down.
Action Items
- •Jochem: Start the AI review pilot as a read-only bot and advance the AGENTS.md guideline (PR 12661, still in draft).
- •Dhanush: Discuss EIP Builder integration with Matt and explore client-side hosting.
- •Pooja: Edit the Keeper of Consensus call for input to reflect a 30-day voting window.
- •Editors: Give PR 12643 (EIP-1 update) its second approval, and finish the Stagnant Bot review.
- •Editors: Add themselves to upcoming office hours to help manage the PR backlog.
Next Meeting
- •EIPIP Meeting #133 · Dec 16, 2026, 16:00 UTC
Key decisions
AI review pilot approved as a read-only bot that posts reviews as comments, with no auto-merging of PRs.
AI review scope is limited to structural and formal checks (backward references, abbreviations, copyright, RFC 2119 keywords), not changes to an author's ideas.
Exceptional merging without author approval is rejected, even for factual corrections, to preserve neutrality and author responsibility.
Editors are open to hosting the EIP Builder on eips.ethereum.org if it is fully client-side, pending a discussion with Matt.
The Keeper of Consensus election remains open for 30 days due to quorum rules.
AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.