I have gone through and updated all existing EIPs to match this rule, including EIP-1.
In some cases, people were using markdown citations, I suspect because the long-form was a bit verbose to inline. Since the relative path is quite short, I moved these to inline but I wouldn't be opposed to putting them back to citation format if that is desired by the authors.
In doing the migration/cleanup, I found some EIP references to EIPs that don't actually exist. In these cases I tried to excise the reference from the EIP as best I could.
It is worth noting that the Readme actually already had this rule, it just wasn't expressed properly in EIP-1 and the "Citation Format" section of the readme I think caused people a bit of confusion (when citing externally, you should use the citation format).
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* EIP-1895: Better constants and address range description
Address @Arachnid's comments about presenting constants and how an address value is limited.
* EIP-1985: Fix a typo
* EIP-1985: Use "instructions" instead of "opcodes"
* sane
* some clarifications
* remove cruft
* some clarifications
* propose spec changes
* limit the scope to EVM only
* more rationale
* group affected opcodes by ranges
* Rename to EIP-1985
* Add discussion URL to EIP-1985
* Include a reference to EIP106
* Add more rationale
* fix typo
* Remove unfounded worry
* mention timestamp being 64-bit value in Aleth
* resolved an TODO item as Rationale entry
