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

784 B

eip title author type status created requires
606 Hardfork Meta: Homestead Alex Beregszaszi (@axic) Meta Final 2017-04-23 2, 7, 8

Abstract

This specifies the changes included in the hard fork named Homestead.

Specification

  • Codename: Homestead
  • Activation:
    • Block >= 1,150,000 on Mainnet
    • Block >= 494,000 on Morden
    • Block >= 0 on future testnets
  • Included EIPs:
    • EIP-2 (Homestead Hard-fork Changes)
    • EIP-7 (DELEGATECALL)
    • EIP-8 (Networking layer: devp2p Forward Compatibility Requirements for Homestead)

References

  1. https://blog.ethereum.org/2016/02/29/homestead-release/

Copyright and related rights waived via CC0.