EIP Improvement Process #128
Transcript
Call summary
Summary
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.
Decisions
- •Keep shared EIP/ERC files (such as EIP-1) in sync via a git submodule or a shared infrastructure repo instead of duplicating PRs; Sam to write up an issue for community help.
- •Move the Glamsterdam-referenced EIPs and the meta EIP to Review (PRs created), with an explicit note that consistency must be resolved before Last Call/Final.
- •Remove the deprecated execution-spec-tests URL from EIP-1 (PR 11845) per the EIP-5757 removal rule; editors can approve it directly (needs two approvals).
- •ETHbot will include authors/co-authors and the merged PR number in its squash-merge commit messages.
- •Disallow external library imports in the Specification section (inline the interfaces), but allow them in the Reference Implementation section.
- •Enforce RFC-2119 normative keywords only in the Specification section; EIPW flags them elsewhere.
- •Do not rename the default branch from master to main, because it would break downstream EIP tooling.
- •Editor merge discretion: for Final EIPs, editors may merge a PR pending author approval for over two weeks (with two editor approvals); for non-final EIPs, editors must not merge without author approval except obvious typo fixes. To be documented formally.
Highlights
- •Glamsterdam: EIP-8037 depends on ~10 EIPs; editors will move the referenced EIPs and the meta EIP to Review (PRs created), with an explicit note that consistency must be fixed before Last Call, then take it to ACD so authors address open PRs.
- •Shared EIP/ERC infrastructure files (e.g. EIP-1) will be kept in sync via a git submodule (or a shared repo) instead of duplicating PRs across both repositories.
- •ETHbot will be changed to include authors/co-authors and the merged PR number in its squash-merge commit messages, for accountability and traceability.
- •Solidity: external library imports are disallowed in the Specification section (interfaces must be inlined) but allowed in the non-normative Reference Implementation section.
- •RFC-2119 keywords (MUST/SHOULD/etc.) are to be enforced only in the Specification section; EIPW should flag normative keywords used elsewhere.
- •Renaming the default branch master to main was rejected because it would break downstream EIP tooling.
- •EIP-7723 (network-upgrade inclusion stages) mixes 'status' and 'stage' and is contradicted by the Fusaka/Glamsterdam metas; fixes go through ACD since this is the fork process, not the editor process.
- •Community demo: EIP Lab (EVVM team) showed an AI tool that reads an EIP and generates mock smart contracts to test it on the EVVM stack (~$5 per iteration); full demo next time.
Action Items
- •Sam - Write up the shared-files (submodule) issue; check the EIPW first-reference-URL rule; review the copyright-waiver PR; approve/merge the Glamsterdam PRs on rebase
- •Yam - Open ETHbot issues (preserve authors/co-authors and PR number in commits) and enforce RFC-2119/8174 URL links
- •Pooja - Move the Glamsterdam EIPs to Review and take them to ACD; create the EIP-7723 fix PRs (status/stage wording, decline-for-inclusion removal timing, core-only scope) and bring them to ACD; document the editor merge-discretion policy
- •Editors - Provide second approvals (call-for-input 393, EIP-1 PR 11845, Glamsterdam PRs) and review/close the five listed issues
Key decisions
Keep shared EIP/ERC files in sync using a git submodule (or a shared infrastructure repo) rather than duplicating PRs across the EIP and ERC repositories.
The EIP/ERC repo split caused drift and double PRs for shared files like EIP-1.Move the Glamsterdam-referenced EIPs and the meta EIP to Review (PRs created), noting that consistency must be resolved before Last Call/Final, then take it to ACD for authors to address open PRs.
EIP-8037 depends on ~10 EIPs; repricing EIPs have conflicting definitions and ongoing spec changes.Change ETHbot to include authors/co-authors and the merged PR number in squash-merge commit messages.
Disallow external Solidity library imports in the Specification section (inline the interfaces) but allow them in the non-normative Reference Implementation section.
Enforce RFC-2119 keywords only in the Specification section; EIPW should flag normative keywords used outside it.
Reject renaming the default branch from master to main, as it would break downstream EIP tooling.
Editors may merge PRs pending author approval only for Final EIPs (after two weeks, with two editor approvals); for non-final EIPs, no merging without author approval except obvious typo fixes. This will be documented formally.
EIPs discussed
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.