As illustrated by Dencun and the Merge, the Ethereum network regularly implements planned forks in an effort to achieve its development roadmap, advance the scalability process, and to improve the network generally. For example, in connection with the Ethereum development roadmap, the Ethereum network executed planned forks to transition from the initial Frontier development stage into the Homestead development stage in 2016; to transition from the Homestead development stage to the first sub-stage, Byzantium, of the Metropolis development stage in 2017; to transition from the Byzantium sub-stage to the St. Petersburg sub-stage in early 2019; and to transition from the St. Petersburg sub-stage to the Istanbul sub-phase, in late 2019. In April 2021, the Ethereum network underwent the Berlin and Altair planned forks, among others. In 2022, Ethereum underwent the Bellatrix and Paris planned forks in connection with the Merge. In 2023, Ethereum underwent the Capella and Shanghai planned forks (collectively, “Shapella”), which enabled withdrawals of staked assets to the Ethereum Layer 1 blockchain mainnet for the first time (they had previously been locked on the Beacon Chain testnet following the Merge). Any of these or future planned forks could fail to work as intended or could introduce bugs, coding defects, unanticipated or undiscovered problems, flaws, or security risks, create problematic economic incentives which incentivize behavior which has a negative effect on the Ethereum network’s nodes, users, validators, or the Ethereum network as a whole, or otherwise adversely affect, the speed, security, usability, or value of the Ethereum network or ether. Alternatively, such hard forks could be contentious, leading to a split and fracture in the Ethereum community to its collective detriment, as discussed above. Any such outcomes could adversely affect the value of the Shares.
Forks may also occur as a digital asset network community’s response to a significant security breach. For example, in July 2016, Ethereum underwent a hard fork between the Layer 1 Ethereum network and a new digital asset running on a “forked” branch of the network, Ethereum Classic, as a result of the Ethereum network community’s response to a significant security breach. In June 2016, an anonymous hacker exploited a smart contract running on the Ethereum network to syphon approximately $60 million of ether held by The DAO, a decentralized autonomous organization, into a segregated account. In response to the hack, and after a contentious debate, most participants in the Ethereum community elected to adopt a hard fork that effectively reversed the hack, and this network constitutes the Layer 1 Ethereum network. However, a minority of users continued to develop the original blockchain, now referred to as “Ethereum Classic,” which is not backwards-compatible with the Layer 1 Ethereum network and is considered a forked branch, with the native digital asset on that blockchain now referred to as Ethereum Classic, or ETC. ETC now trades on several digital asset platforms. Following the July 2016 hard fork between the Ethereum and Ethereum Classic networks, new security concerns surfaced. Replay attacks, in which transactions from one network were rebroadcast to nefarious effect on the other network, plagued Ethereum exchanges through at least October 2016. An Ethereum exchange announced in July 2016 that it had lost 40,000 Ethereum Classic, worth about $100,000 at that time, as a result of replay attacks. Similar replay attack concerns occurred in connection with the Bitcoin Cash and Bitcoin Satoshi’s Vision networks split in November 2018, and security concerns could similarly surface in connection with future hard forks.
An unplanned fork may also occur as a result of an unintentional or unanticipated software flaw in the various versions of Ethereum Client software that nodes run and use to access the Ethereum network. For example, such an unplanned fork reportedly occurred in the Go-Ethereum (“Geth”) client, which is a popular Ethereum Client that many nodes use to access the Ethereum network and whose developers are financially supported by the Ethereum Foundation. In November 2020, a bug was discovered in Geth (but not the other Ethereum Clients at the time, such as Besu, OpenEthereum, and Nethermind), and a patch was released that all nodes using the Geth client were supposed to download and apply simultaneously. However, not all nodes using Geth did so, resulting with the non-patched Geth nodes temporarily running a different version of the Ethereum blockchain than the patched Geth nodes and nodes using other Ethereum Clients. This temporarily created two conflicting versions of the Ethereum blockchain, causing the nodes using the non-patched Geth version to be unable to reach consensus with the rest of the nodes on the Ethereum blockchain, interrupting the non-patch Geth nodes’ access to the Ethereum network. For example, Infura, which is a node operator that provides services to major Ethereum smart contracts, wallet software providers like MetaMask, ether trading platforms, and other market participants, reportedly ran numerous nodes using the Geth client. Infura’s Geth client-running nodes reportedly used the outdated, non-patched Geth version initially, which is said to have caused those nodes to be on the minority blockchain, impacting transaction execution, validation, and recording on the main Layer 1 Ethereum network for Infura’s customers - such as Ethereum-based smart contracts, wallet providers like MetaMask, ether trading platforms, etc. - until Infura was able to apply the software update released by the Geth client developers to Infura’s nodes that use Geth as their Ethereum Client. Ultimately, the problem was reportedly fixed by releasing a new upgraded version of Geth that all nodes using the Geth client were to promptly download. This reportedly harmonized the conflicting versions and restored synchronization among Geth nodes, fixing the problem and restoring access to the Ethereum network, including for Infura and its customers.
37