EIP-609 Hard fork meta: Byzantium ("Hardfork Meta: Byzantium")
Final · Other · EIP status Final · created 2017-04-23
A meta EIP that finalizes and records the 9 EIPs included in the 2017 Byzantium hard fork and their activation block. It took effect starting at mainnet block 4,370,000.
Why it is needed
Ethereum uses a mechanism called a hard fork to change network rules. A hard fork is an upgrade in which all nodes switch to new rules at once starting from a specified block number. If the changes included and the block at which they activate differ between node software (clients), the network can split in two. That is why a meta EIP is needed to fix, in a single official document, the list of EIPs included in a fork and their activation point. EIP-609 is the document that records the changes included in the Byzantium hard fork. Byzantium is also called Metropolis part 1. It bundled together 9 EIPs covering new EVM opcodes, precompiled contracts for cryptographic operations, changes to the difficulty adjustment method and block reward, and improvements to transaction receipts.
What changes
Today
- Smart contract execution had no opcodes such as REVERT, STATICCALL, RETURNDATASIZE, or RETURNDATACOPY
- There were no precompiled contracts for alt_bn128 elliptic curve operations or big integer modular exponentiation
- Transaction receipts did not contain a status code indicating success or failure
- Difficulty adjustment did not target an average block time that accounts for uncle blocks
After EIP-609
- REVERT, STATICCALL, RETURNDATASIZE, and RETURNDATACOPY opcodes are added to the EVM
- Precompiles for alt_bn128 addition, scalar multiplication, and pairing check, as well as bigint modular exponentiation, are added
- Transaction status codes are recorded in receipts
- The difficulty adjustment method changes, the difficulty bomb is delayed, and the block reward is reduced
Who is affected
- Client teams: All 9 EIPs had to be implemented and activated simultaneously at mainnet block 4,370,000 and Ropsten block 1,700,000.
- Contract developer: New opcodes such as REVERT and STATICCALL, along with cryptographic precompiles, became usable in contracts.
- Miners: It was affected by EIP-100's difficulty adjustment change and EIP-649's difficulty bomb delay and block reward reduction.
- Wallet & app developers: EIP-658 added a transaction status code to receipts, making it possible to check the processing result from the receipt.
In depth
Role as a meta EIP and activation conditions
EIP-609 does not directly define new features. It is a meta document that fixes which EIPs are included in a given hard fork and at which block they activate. The codename is Byzantium, with aliases Metropolis/Byzantium and Metropolis part 1. The activation condition is mainnet block 4,370,000 or later, and Ropsten testnet block 1,700,000 or later. The included EIPs are 100, 140, 196, 197, 198, 211, 214, 649, and 658, nine in total. The detailed specification of each change is not in this document but in the original text of each included EIP.
New EVM opcodes: EIP-140, 211, 214
Three sets of new opcodes are added to the EVM (Ethereum Virtual Machine). EIP-140 introduces the REVERT opcode, which reverts execution. EIP-211 adds two opcodes, RETURNDATASIZE and RETURNDATACOPY, for handling the return data from a call. EIP-214 adds the STATICCALL opcode. This meta document only records the title of each opcode; the behavioral specification and gas costs are defined in each original EIP.
Cryptographic precompiles: EIP-196, 197, 198
Three kinds of precompiled contracts are added. EIP-196 introduces precompiles for addition and scalar multiplication on the alt_bn128 elliptic curve, and EIP-197 introduces a precompile for an optimal ate pairing check on the same curve. EIP-198 adds a precompile for big integer modular exponentiation (bigint modular exponentiation). Precompiles are a way for clients to implement, in native code at a specific address, operations that would be too costly to write as EVM bytecode.
Difficulty and reward changes: EIP-100, 649
Two mining-related changes are included. EIP-100 changes the difficulty adjustment method to target an average block time that accounts for uncles. EIP-649 delays the Difficulty Bomb and reduces the block reward. This meta document only records the titles of the two EIPs; specific figures such as the delay period or reward amount are defined in each original EIP.
Recording status codes in receipts: EIP-658
EIP-658 adds a transaction status code to the receipt. A receipt is the record left after a transaction is processed, and from Byzantium onward it includes a code indicating the processing status. The detailed specification, such as the values and encoding of the status code, is defined in the original EIP-658 text.
Document status and references
The status of this EIP is Final. It is a record of a past hard fork whose activation has already completed, so its content will not change further. The requires field lists EIP-607 in addition to the 9 included EIPs. The references include a link to the Ethereum Foundation blog's Byzantium hard fork announcement dated October 12, 2017. Copyright is waived under CC0.