Clients (3 of 5)

Ethereum's genetic material specifies how any client may be implemented on Ethereum, regardless of the underlying codebase (see "WPYP Chromosome" in Ethstory Series 1). This early "branching" strategy has yielded benefits. For example, in 2016, as developers worked to keep Go Ethereum ("geth") more resistant to DDoS-like attacks, nodes using Parity's Rust-based Ethereum client kept churning, maintaining the network. Each implementation makes the network less vulnerable. On this original, these two historic clients are shown in their early forms. Over 40,000 code items are adapted from early client versions and visualized here. Key concepts among variables are highlighted, and code runs from left to right, outside in. In green, the Go Ethereum implementation; in red, the Rust-based Parity implementation. They are separate clients, helping to expand Ethereum's blockchain, but they are both built on the backdrop of the yellow paper, and both stay aligned within its specifications. In the PDF, it is possible to zoom in on individual bits of code at perfect image quality, or to zoom out and see a kind of texture of code reflecting this branching, diversified implementation strategy.

• 5 editions
• Square, high-quality JPG (linked in unlockable content)
• Scalable vector-quality PDF (linked in unlockable content)

Ethstory, Original 1 in Series 2: "0xBB9bc (Branching)"

It is in Ethereum's nature to expand and diversify, to branch and bring into existence new varieties, new experiences. This second series "0xBB9bc (Branching)" is brighter than the first, signaling a kind of "turning on the light," actualizing and perceiving these rapidly branching projects. All 4 originals were generated using thousands of pieces of data drawn from primary sources, including Ethereum documentation and on-chain activity.