7 Commits

Author SHA1 Message Date
Mikhail Melnik
792ac79ca5
fix link to berlin.md (#3498) 2021-04-16 14:10:58 +08:00
Alex Beregszaszi
7874ef7aaa
Update EIP-2070 pointing to eth1.0-specs (#3305) 2021-03-02 13:29:53 +08:00
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
Pooja Ranjan
d3756c0998
Update eip-2070.md (#2806)
Changed timeline.
2020-07-21 09:42:33 +08:00
Alex Beregszaszi
425d7db297
Fixes to EIP-2070 (#2650) 2020-05-17 12:56:45 +01:00
Pooja Ranjan
c1008fe312
Automatically merged updates to draft EIP(s) 2070 (#2589)
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
2020-05-16 10:40:19 +12:00
Alex Beregszaszi
54ad231616
Add hardfork meta after Istanbul (Berlin) (#2070)
* Add hardfork meta after Istanbul (Berlin?)

* Rename to EIP-2070

* Add discussion URL

* Add in tentatively accepted EIPs from Istanbul
2019-09-05 11:46:38 +01:00