Andreas Bigger

How blockchain nodes find each other with no directory, the two ways peers exchange data, and how a Base node runs two separate p2p networks at once, one for execution and one for consensus.

How a rollup proves it ran correctly with a program that never touches the network, and a one-line bug in how it reads its own config that can silently poison a multi-hour proof.

How Base schedules a hardfork by writing it to a contract on Ethereum instead of baking a timestamp into every node, why the reads fail closed, and why the proof has to agree on the same schedule.

base/base runs four tiers of tests and none of them measure speed. Adding performance as a fifth tier, and the harder problem underneath: making a wall-clock benchmark on shared CI hardware trustworthy enough to comment on a pull request.

A routine version bump. A database that wouldn't open. And a linker three years out of date, hiding in a build container nobody had looked at since the day it was written.