6 Commits

Author SHA1 Message Date
Micah Zoltu
15f61ed0fd
Adds rule to EIP-1 that references to other EIPs must use relative path format and the first reference must be linked. (#2947)
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).
2020-09-30 12:22:43 +08:00
Nick Gheorghita
9234722c4c
Update username in EIP-1319 (#2550) 2020-09-08 20:33:07 +01:00
William Entriken
d5259bc809 Fix spelling of GitHub [R4R] (#2369) 2019-11-22 21:02:58 +00:00
Nick Gheorghita
3e04ff2189 Minor updates to EIP-1319 (#1966) 2019-04-24 19:29:36 +02:00
Nick Gheorghita
123b7267b6 Proposal to add numPackageIds() and numReleaseIds() (#1609) 2019-03-14 22:33:06 +01:00
c-g-e-w-e-k-e-
0469efa837 ERC 1319 Smart Contract Package Registry Interface (#1320)
* ERC 1319

* Make generateReleaseId public view
2018-08-28 12:35:55 +01:00