Skip to content

EIP-7199: Linter Scope

Relax the policy for updating EIP.

⚠️ DraftMeta

Draft Notice

This EIP is in the process of being drafted. The content of this EIP is not final and can change at any time; this EIP is not yet suitable for use in production. Thank you!

AuthorsZainan Victor Zhou (@xinbenlv)


Currently in practice EIP linter tools (EIPW, for example) will block a Pull Request for lint errors even if that lint errors was not introduced in that Pull Request. This EIP make it explicit that lint errors for untouched lines shall be considered ignoreable except for status change.


The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

In an update to an EIP, A Pull Request SHOULD NOT be required to fix linter errors in untouched lines unless it's changing the Status of the EIP.


This policy allows micro contributions for anyone who just want to fix a typo or change a section of a section in a large EIP.

Security Considerations


Copyright and related rights waived via CC0.


Please cite this document as:

Zainan Victor Zhou, "EIP-7199: Linter Scope[DRAFT]," Ethereum Improvement Proposals, no. 7199, 2023. [Online serial]. Available: