EIPs/EIPS/eip-2070.md
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

1.2 KiB

eip title author discussions-to type status created requires
2070 Hardfork Meta: Berlin Alex Beregszaszi (@axic) https://ethereum-magicians.org/t/hardfork-meta-eip-2070-berlin-discussion/3561 Meta Draft 2019-05-20 1679

Abstract

This meta-EIP specifies the changes included in the Ethereum hardfork named Berlin.

Specification

  • Codename: Berlin
  • Activation: TBD

Included EIPs

  • TBD

Accepted EIPs

Proposed EIPs

  • EIP-2046: Reduced gas cost for static calls made to precompiles
  • EIP-2565: Repricing of the EIP-198 ModExp precompile

Timeline

(Proposed)

  • Testnets - TBD
  • Mainnet - TBD

References

Copyright and related rights waived via CC0.