EIP-1679 Hardfork meta: Istanbul ("Hardfork Meta: Istanbul")
Final · Other · EIP status Final · created 2019-01-04
A Meta-type EIP that finalizes and records the six EIPs included in the Istanbul hardfork along with their activation block numbers on mainnet and the testnets.
Why it is needed
Ethereum upgrades via hardforks, where every node on the network switches to new rules simultaneously once a set block number is reached. If which changes go into a given fork and when they activate aren't recorded in one place, different clients (node software) risk applying different rules and causing a chain split. Individual EIPs only describe their own changes and don't indicate which fork they ship with. So for each fork, a Meta EIP is used to pin down the inclusion list and activation timing in an official document. EIP-1679 is the Meta EIP for the hardfork named Istanbul, recording the six included EIPs and their activation block numbers across mainnet and four testnets. The inclusion list is carried over directly from what core developer calls finalized.
What changes
Today
- Changes going into Istanbul were scattered across individual EIP documents and discussion threads
- There was no official document for checking activation timing across networks at a glance
- Each client team had to track implementation scope separately
After EIP-1679
- The six included EIPs are recorded as a single finalized list
- Activation block numbers are specified for mainnet and four testnets
- All client teams implement against the same document
Who is affected
- Client teams: Implementations build and ship Istanbul support based on the inclusion list and block numbers in this document.
- Node operators: Clients must be upgraded before the activation block to avoid falling off the network.
- Contract and app developers: Among the included EIPs, the gas cost changes (EIP-1108, 1884, 2028, 2200) affect the execution cost of existing contracts.
- Users: The fork itself applies automatically, and the changed gas costs are reflected indirectly in fees.
In depth
The role of a Meta EIP
Beyond documents proposing protocol changes, EIPs include a Meta type that records procedures or bundles. EIP-1679 is a Meta type that specifies which EIPs are included in the hardfork codenamed Istanbul. The technical content of each individual change is covered by its own EIP, while this document only finalizes coordination information: the inclusion list and activation conditions. Its status is Final.
Activation block numbers
Istanbul activates at the following blocks per network: mainnet Block >= 9,069,000, Ropsten testnet Block >= 6,485,846, Kovan testnet Block >= 14,111,141, Rinkeby testnet Block >= 5,435,345, Görli testnet Block >= 1,561,651. Testnets are assigned activation blocks ahead of mainnet, following the order of verifying client implementations before mainnet deployment.
EIPs that add functionality: 152, 1108, 1344
EIP-152 adds the Blake2 hash function's compression function F as a precompile. EIP-1108 lowers the gas cost of the alt_bn128 elliptic curve precompiles (though a cost reduction, this is largely a functional change since it makes zero-knowledge-proof-style operations using that precompile practical). EIP-1344 adds the ChainID opcode to the EVM, which identifies the current chain.
EIPs that adjust gas costs: 1884, 2028, 2200
EIP-1884 reprices gas costs for opcodes whose cost depends on state trie size. EIP-2028 lowers the gas cost of calldata, the data carried in a transaction. EIP-2200 rebalances net-metered SSTORE gas costs to reflect the SLOAD cost change from EIP-1884. All three change the execution cost of existing contracts and can affect code tightly tuned to gas limits.
The requires list and EIP-1716
The requires field in the original preamble lists EIP-1716 alongside the six included EIPs (152, 1108, 1344, 1884, 2028, 2200). EIP-1716 does not appear in the Included EIPs list and appears only in requires, indicating a dependency notation: the Istanbul spec presupposes the preceding document EIP-1716. The original body does not separately describe EIP-1716's content.
How the inclusion list was finalized
The list of included EIPs was finalized at All Core Devs Call #68, and the original References cite that call's minutes as the basis. Also cited is a post by the Ethereum Cat Herders, 'Istanbul testnets are coming,' a reference covering the testnet rollout process. Since this EIP's status is Final, the list and block numbers are a finalized record that will not change further.