logo
TradFi
Sign Up to 15,000 USDT in Rewards
Limited-time offer is waiting for you!

Who Is Gavin Andresen? Former Bitcoin Core Lead Developer

Key Points

Who is Gavin Andresen? The developer who led Bitcoin's early code. His merges and BIPs, his emails with Satoshi and where he went next.

Gavin Andresen is a software developer who served as lead developer of Bitcoin Core, Bitcoin's reference software, until he handed the job on in April 2014. He was also chief scientist of the Bitcoin Foundation, and in October 2025 he wrote that he was retired from crypto and building RiskiPedia, a wiki about everyday risks.

In 2011 Andresen made more merges into Bitcoin's main code than any other developer, about 45% of the year's total. He also wrote 9 of the 31 Bitcoin Improvement Proposals numbered from 2011 to 2013, more than any other author. After he handed the maintainer role to Wladimir van der Laan in April 2014, his merges thinned out and stopped in May 2015.

Year
His merges, of all merges
His BIPs, of that year's BIPs
2010
42 of 42, all syncs from Subversion
None
2011
141 of 316 (44.6%)
3 of 8
2012
157 of 691 (22.7%)
2 of 16
2013
209 of 624 (33.5%)
4 of 7
2014
64 of 1,008 (6.3%)
1 of 10
2015
3 of 762 (0.4%)
1 of 31
2016
0 of 990
1 of 18
 

Who Is Gavin Andresen?

Andresen ran the day-to-day work on Bitcoin's main software through its early growth. In an April 2014 post on the Bitcoin Foundation's blog, he wrote that for the previous 18 months he had filled two roles, "lead developer" for Bitcoin Core and "Chief Scientist" for the Foundation.

As lead developer he merged other people's changes into the code. Handing that role on, he wrote, would leave him a little less time "writing Bitcoin Core release announcements" and more for protocol questions that cut across different Bitcoin programs. The Foundation was a membership group, and his post thanked its members for helping to fund core development.

His name also runs through two of Bitcoin's longest arguments, the identity of Satoshi Nakamoto and the size of its blocks.

How Much of Bitcoin's Code Did Gavin Andresen Merge?

A merge is the step that accepts a proposed change into shared code. Counting every merge in the main branch of the bitcoin/bitcoin repository, the home of Bitcoin Core on GitHub, shows how Andresen's part grew and then ended.

His 42 merges of 2010 were all of one kind. Each copied new work from the project's older Subversion repository into its git copy. Most of that work was Satoshi Nakamoto's, whose names sit on 223 of the 305 commits stamped 2010.

The real gatekeeping began in 2011. Andresen made 141 of that year's 316 merges, ahead of Jeff Garzik with 93 and van der Laan with 42. He wrote about 23% of 2011's commits, so his share of the merges ran at almost twice his share of the writing.

Van der Laan overtook him in 2012 with 247 merges to Andresen's 157, though Andresen's busiest year was 2013 with 209. After the April 2014 handover he made 35 more merges that year, and the last three came in May 2015.

Bitcoin Improvement Proposals (BIPs) are the written specs for changes to Bitcoin, and an official archive lists each one's authors and status. Of the 31 that the archive numbers from 2011 to 2013, Andresen wrote 9, ahead of Luke Dashjr with 6.

Later BIPs came mostly from others, among them Bitcoin Core developer Pieter Wuille, a co-author of the 2015 SegWit proposal.

Does Gavin Andresen Know Satoshi?

Andresen knew Satoshi Nakamoto as an email correspondent. Writing in May 2016, he called Satoshi the person he had "communicated with in 2010 and early 2011". A 2022 post on his blog reproduced what he called their last email exchange, dated 26 April 2011.

In it Satoshi wrote, "I've moved on to other things and will probably be unavailable," and he sent along "the CAlert key and broadcast code in case you need it." Bitcoin's code of that time describes alerts as signed messages broadcast across the network to tell users of old versions to upgrade.

In his May 2016 post Andresen wrote that he believed Craig Steven Wright was the person who invented Bitcoin. In February 2023 he added a note above it that reads, "I now know it was a mistake to trust Craig Wright as much as I did." The note says he regrets getting drawn into the "who is (or isn't) Satoshi" game and refuses to play it any more.

Gavin Andresen's Career: Lead Developer and Foundation Chief Scientist

Andresen's first commit to Bitcoin's code is a line-ending fix titled "Fix CRLF", dated 14 July 2010, the day his GitHub account opened. GitHub credits that account with 1,101 commits to the project.

His early proposals dealt with coins that need more than one signature to spend. BIPs 11 to 13 got their numbers in October 2011, and BIP 11's own example is an escrow in which any two of a buyer, a seller and a dispute agent can release the coins.

A deal that settles once the right keys sign is a basic smart contract, a term the scientist Nick Szabo coined.

BIP 16, his Pay to Script Hash design, followed in January 2012 and carries the status Deployed. It lets the person receiving coins set the conditions for spending them behind a short hash, so the sender's wallet doesn't have to handle a complicated script.

By April 2014 van der Laan had been paid to work on Bitcoin Core full time for several months. Andresen's handover post said van der Laan had agreed to take over as "Bitcoin Core Maintainer," and it added, "I'm not going to disappear."

The block-size debate came next. In June 2015 Andresen proposed BIP 101, which would have lifted Bitcoin's one-megabyte block limit to eight megabytes and doubled it every two years. BIP 109, in January 2016, asked for a one-time rise to two megabytes. Both were hard forks, rule changes that older node software would reject. Neither is in use, and the archive marks both Closed.

The last commit he wrote, a unit test from February 2016, entered Bitcoin Core's main code in May 2016 through a merge by van der Laan.

Where Is Gavin Andresen?

In October 2025 Andresen announced RiskiPedia, a wiki that lets readers explore everyday risks, as his "latest project". The same post says it "has nothing to do with Bitcoin or cryptocurrencies" and will have no token and no fundraising, and it asks anyone contacted by someone claiming otherwise in his name to ignore them.

"I'm retired from all things crypto," he wrote. That makes any RiskiPedia token pitched in his name a fake by his own account.

As late as October 2026, the newest entry on his blog index was a January 2026 post about building RiskiPedia pages with an AI coding tool. His old blog address forwards to riski.wiki, a site that could not be reached in mid-November 2026.

How to Trade Bitcoin Futures on Phemex

Bitcoin runs on software Andresen helped build, and on Phemex its price trades as BTC/USDT futures, contracts that follow bitcoin's price without you holding any coins. They're perpetual contracts with no expiry date, so funding ratespaid between long and short traders keep their price close to bitcoin's own.

Futures use leverage, and a leveraged position is closed automatically if losses push its margin below a set minimum. That automatic exit is liquidation in crypto trading, and it can cost the whole margin behind a position.

You can go long if you expect bitcoin to rise or short if you expect a fall, and a stop-loss order can close the trade at a price you set in advance.

Frequently Asked Questions

Did Gavin Andresen talk to the CIA?

He agreed to. His April 2011 email says he would speak at an annual conference In-Q-Tel ran for US intelligence agencies. He called In-Q-Tel "a US-govt-funded 'strategic investment' company", writing that "'Gavin openly visits the CIA' will create enough conspiracy theories as it is."

Is Gavin Andresen still a Bitcoin developer?

No. Andresen stopped merging code in May 2015, and his final authored change reached Bitcoin Core a year later. His October 2025 RiskiPedia post says he's "retired from all things crypto."

What BIPs did Gavin Andresen write?

Andresen wrote 12, all on his own except BIP 70, a payment protocol he wrote with Mike Hearn. Nine carry the Deployed status, BIP 16's Pay to Script Hash among them. The three marked Closed are BIP 12's early OP_EVAL idea and his block-size proposals, BIPs 101 and 109.

 

Disclaimer: This article is for informational purposes only and is not financial advice. Cryptocurrency trading involves substantial risk. Always do your own research before making investment decisions.

Sign Up and Claim 15000 USDT
Disclaimer
This content provided on this page is for informational purposes only and does not constitute investment advice, without representation or warranty of any kind. It should not be construed as financial, legal or other professional advice, nor is it intended to recommend the purchase of any specific product or service. You should seek your own advice from appropriate professional advisors. Products mentioned in this article may not be available in your region. Digital asset prices can be volatile. The value of your investment may go down or up and you may not get back the amount invested. For further information, please refer to our Terms of Use and Risk Disclosure