EIP-606 Hard Fork Meta: Homestead ("Hardfork Meta: Homestead")
Final · Other · EIP status Final · created 2017-04-23
A meta document specifying the changes included in the Homestead hard fork. It records that, along with the activation block, three EIPs are included: EIP-2, EIP-7, and EIP-8.
Why it is needed
A hard fork is an upgrade that changes network rules, so every node must apply the same change at the same block or the chain will split. That requires a document that clearly states which change takes effect starting at which block. EIP-606 is the document that specifies which EIPs are included in the hard fork named Homestead. It records in standard form that on mainnet it activates starting at block 1,150,000, and that the included changes are three EIPs: EIP-2 (Homestead Hard-fork Changes), EIP-7 (DELEGATECALL), and EIP-8 (networking layer compatibility requirements). This lets any client team or anyone checking past upgrade history confirm the scope of Homestead from this single document.
What changes
Today
- The changes in EIP-2, EIP-7, and EIP-8 had not yet been applied to the network
- There was no standard document laying out what changes went into the Homestead fork and when it turned on
After EIP-606
- Starting at mainnet block 1,150,000, the three EIPs all activate together at the same point
- The fork name, the per-network activation block, and the list of included EIPs are all recorded in the single document EIP-606
- The Morden testnet applies the same rule starting at block 494,000, and later new testnets apply it starting at block 0
Who is affected
- Client teams: Implementers use this document as the basis for deciding which rules to turn on at which block height.
- Developers and researchers: It serves as the official record for tracking what was included in past upgrades.
- Ordinary users: There is nothing to do directly. Once nodes are upgraded, the new rules apply automatically.
In depth
The meta EIP document format
EIP-606's type is Meta. It is not a document directly proposing a new feature at the code level, but one that specifies the changes included in the hard fork named Homestead. The Abstract states only this point in a single sentence. The codename is Homestead, the author is Alex Beregszaszi (@axic), and the document was created on 2017-04-23. The requires field lists EIP-2, EIP-7, and EIP-8, making clear from the frontmatter that this meta document presupposes these three EIPs.
Activation condition: per-network block height
The activation condition is specified differently for each network. On Mainnet it activates at block 1,150,000 or above, and on the Morden testnet at block 494,000 or above. On future testnets it activates at block 0 or above, meaning the Homestead rules apply from the very start. Because activation is based on block height, all nodes switch to the new rules simultaneously at the same block.
The three included EIPs
Three EIPs are included in Homestead. EIP-2, titled 'Homestead Hard-fork Changes,' contains the changes for the Homestead hard fork. EIP-7 covers DELEGATECALL. EIP-8, titled 'Networking layer: devp2p Forward Compatibility Requirements for Homestead,' covers forward compatibility requirements for the devp2p networking layer. The detailed specification of each of the three EIPs lives in their respective source documents, and EIP-606's role is to bundle this list with the activation block to finalize the fork's scope.
Status Final and references
The document's status is Final, meaning the content is settled and will not change further. The References section links to a single Ethereum Foundation blog post covering the Homestead release (the homestead-release post on blog.ethereum.org). The copyright is waived under CC0, so anyone may use it freely. There is no separate core developer call decision record related to this explainer.