Linux kernel developer and early Bitcoin contributor
In July 2010, a Red Hat Linux kernel developer named Jeff Garzik read a Slashdot post about Bitcoin, pulled the codebase, and started sending patches. Within months he had become the top non-Satoshi commit-count contributor, ranking just behind Satoshi and Gavin Andresen. He wrote cpuminer (one of the first standalone Bitcoin mining tools), authored multiple BIPs including the BIP 100 dynamic-block-size proposal, and co-founded the enterprise-blockchain firm Bloq in 2015.
Garzik studied computer science at Georgia Institute of Technology and built his early career on Linux-kernel work at Red Hat. His kernel-level systems experience translated directly to Bitcoin’s C++ codebase.
The July 2010 Slashdot post that reached Garzik covered Bitcoin’s v0.3 release — a traffic surge early developers later called “the Great Slashdotting,” and the moment a wave of programmers first found the project. Garzik was one of them, and his kernel background let him start reading and patching the C++ code right away.
Garzik became one of the top three contributors to Bitcoin Core by commit count — behind only Satoshi Nakamoto and Gavin Andresen — and was among the earliest developers granted commit access to the repository, added as a GitHub committer on May 6, 2011 when development moved off SourceForge. His first major work went after the part of the client that hurt new users most: he rewrote the initial blockchain download to run 10x to 100x faster — though the contemporaneous v0.3.18 SourceForge release notes describe this same category of work more modestly, as speeding up the initial block download only “a little.”
Garzik created cpuminer, widely used open-source software for CPU mining Bitcoin. The tool was one of the first standalone mining applications, enabling users to mine without running the full Bitcoin client.
The working relationship played out over email and patch submissions: Garzik would write a change, test it, turn it into a patch, and send it to Satoshi; if Satoshi accepted it, the code went into the project’s Subversion repository. Garzik later described Satoshi as “practical and sane, which made interactions very easy and comfortable” — a collaborator whom, by his account, early contributors knew only “through his contributions on mailing lists and forums.”
Garzik authored multiple Bitcoin Improvement Proposals (BIPs), including BIP 100, which proposed a dynamic block size limit determined by miner voting. His scaling proposals were part of the broader debate about Bitcoin’s transaction capacity that became a central issue in the Bitcoin community.
Garzik’s own technical eye also caught one of Bitcoin’s earliest critical bugs: on August 15, 2010, he was the technical observer who first spotted the value-overflow anomaly in a raw block dump, posting the public warning that triggered Satoshi’s patch within hours.
In 2015 Garzik co-founded Bloq, an enterprise blockchain firm, and later led Hemi Network. His scaling work — BIP 100 above all — kept him in the larger-block, throughput-first camp of the capacity debate that dominated Bitcoin’s middle years: he was part of the New York Agreement compromise group in 2017 and one of the co-signers of the message that eventually cancelled the SegWit2x hard fork.
56 entries
Doubters called it unscalable in 2008. A famed hacker failed to break the code. A judge, a dictionary, and a Nobel nominator weighed in. What others said about Satoshi, read as one record.
Structural reading of the 2010-08-15 overflow incident — soft-fork rescue mechanics, why a 5-hour response was only achievable then, transaction-shape forensics, and the centralization paradox.
Jeff Garzik posts the first public alert of the value-overflow incident, sharing the raw block data for #74638 with two outputs of 92,233,720,368.54277039 BTC each.
PR #91 thread starter by jgarzik in bitcoin/bitcoin.
PR #1367 thread starter by jgarzik in bitcoin/bitcoin.
Comment by jgarzik in bitcoin/bitcoin PR #2161. context for Satoshi mention.
Context post by jgarzik in BitcoinTalk topic 556. after msg5443.
Context post by jgarzik in BitcoinTalk topic 576. after msg5904.
Context post by jgarzik in BitcoinTalk topic 626. quotes Satoshi.
Context post by jgarzik in BitcoinTalk topic 296. after msg3495.
Context post by jgarzik in BitcoinTalk topic 648. after msg7084.
Context post by jgarzik in BitcoinTalk topic 750. after msg8140.
Context post by jgarzik in BitcoinTalk topic 941. after msg11439.
Context post by jgarzik in BitcoinTalk topic 999. after msg12181, quotes Satoshi.
Context post by jgarzik in BitcoinTalk topic 665. after msg18508.
Context post by jgarzik in BitcoinTalk topic 2162. after msg28549, quotes Satoshi.
Context post by jgarzik in BitcoinTalk topic 1901. after msg23891.
Context post by jgarzik in BitcoinTalk topic 1790. after msg28696, quotes Satoshi.
Context post by jgarzik in BitcoinTalk topic 1007. after msg12262.
Context post by jgarzik in BitcoinTalk topic 1528. after msg17924.
Thread starter by jgarzik in BitcoinTalk topic 611.
Thread starter by jgarzik in BitcoinTalk topic 1925.
Quoted post by jgarzik in BitcoinTalk topic 1735.
Quoted post by jgarzik in BitcoinTalk topic 612.
Quoted post by jgarzik in BitcoinTalk topic 689.
Quoted post by jgarzik in BitcoinTalk topic 691.
Context post by jgarzik in BitcoinTalk topic 628. before msg6508.
Context post by jgarzik in BitcoinTalk topic 632. before msg7090.
Context post by jgarzik in BitcoinTalk topic 760. before msg8413.
Context post by jgarzik in BitcoinTalk topic 589. before msg12483.
Context post by jgarzik in BitcoinTalk topic 784. before msg8651.
Context post by jgarzik in BitcoinTalk topic 807. before msg9134.
Context post by jgarzik in BitcoinTalk topic 823. before msg9531.
Context post by jgarzik in BitcoinTalk topic 928. before msg11400.
Context post by jgarzik in BitcoinTalk topic 1375. before msg15682.
Context post by jgarzik in BitcoinTalk topic 685. before msg7331.
Context post by jgarzik in BitcoinTalk topic 645. quoted by msg8137.
Context post by jgarzik in BitcoinTalk topic 721. before msg8114.
Context post by jgarzik in BitcoinTalk topic 765. before msg8422.
Context post by jgarzik in BitcoinTalk topic 795. before msg8960.
Context post by jgarzik in BitcoinTalk topic 806. quoted by msg9475.
Context post by jgarzik in BitcoinTalk topic 820. before msg9655.
Context post by jgarzik in BitcoinTalk topic 921. before msg11345.
Context post by jgarzik in BitcoinTalk topic 2151. before msg28228.
Bitcoin's migration from SourceForge SVN to GitHub, and the chronological record of developers who received commit access to the GitHub repository in 2011.
Jeff Garzik suggests users increase transaction fees if confirmations are slow, and notes that specialized software for non-currency transactions would provide user-friendly fee interfaces.
Benjamin Wallace's Wired feature — an early major mainstream article on Bitcoin. Traces the whitepaper, mining boom, Mt. Gox hack, and growing pains, ending with Garzik's "We really don't care."
Jeff Garzik starts a discussion: RFC: remove DB_PRIVATE flag.
Jeff Garzik starts a discussion: Always pay transaction fee?
Jeff Garzik starts a discussion: Prioritized transactions, and tx fees.
Jeff Garzik starts a discussion: [PATCH] increase block size limit.
Jeff Garzik starts a discussion: Transaction / spam flood attack currently under way.
Jeff Garzik starts a discussion: RFC: ship block chain 1-74000 with release tarballs?
Early Bitcoin developer Jeff Garzik released videos detailing his time working with Satoshi, describing the creator as a self-taught, solitary genius who never revealed any personal information.
An integer overflow (CVE-2010-5139) let Block 74638 create 184 billion BTC. Satoshi released a fix 5h 40m after discovery; the fixed chain overtook the bad one about 15 hours after the block.
Jeff Garzik, one of Bitcoin's earliest core developers, reflects on his work with Satoshi. He discovered Bitcoin via a July 2010 Slashdot post and became one of the top three contributors.