Byzantium Fork

Overview

Byzantium was an Ethereum hard fork activated at mainnet block 4,370,000 in October 2017. It implemented part of the Metropolis upgrade, including new opcodes, changes to transaction receipt handling, precompiles supporting zk-SNARK verification, and improvements to smart-contract error behavior. The fork also delayed the difficulty bomb and reduced the block reward from five ETH to three ETH. Nodes that did not adopt the new rules could no longer validate the same post-fork chain correctly.

Historical indexers and replay systems need fork-aware execution because identical bytecode can behave differently across protocol eras. The name describes a rule activation, not a separate current network. Modern Ethereum clients include Byzantium’s changes as part of later consensus history. Deposits and payouts need heightened monitoring around activation, and confirmation policies should account for delayed finality, client disagreement, or temporary service suspension without duplicating or losing transactions. Payment systems should treat Byzantium Fork as a controlled operational event. Historical references to Byzantium Fork should distinguish the rules introduced at activation from later changes that modified or replaced them. Current behavior must be verified against the active specification and client release rather than inferred from the original upgrade announcement.

A fork name alone does not show whether a node has activated the change, whether another chain adopted it differently, or whether historical documentation still matches the live network. Byzantium Fork should be documented with its target network, activation condition, affected rules, and compatible software versions.

Practical implication: Byzantium permanently changed Ethereum execution and economics, making fork-aware rules essential for historical block and transaction replay.