Gavin Andresen
https://youtu.be/EOQee-JVUdA

Gavin Andresen Steps Down as Bitcoin’s Lead Developer.
Apr 8, 2014
Kadhim Shubber

Bitcoin’s new lead developer Wladimir van der Laan tells CoinDesk via email he was “surprised” to be offered the role and hadn’t expected Gavin Andresen to step down:

“I had noticed that Gavin had been much less active in the Github project lately, but I did not expect him to step down as lead developer. But it makes sense, there is a lot more theoretical work with regard to Bitcoin and cryptocurrency in general making it a full-time job just to keep up with that (and giving talks, travelling, and such). On the other hand, I have been effectively the maintainer of the code for quite a while. In practice nothing changes.”

Wladimir van der Laan, a Dutch computer scientist with a PhD in computer graphics from University of Groningen, will be taking over as Bitcoin Core Maintainer"

https://www.coindesk.com/gavin-andresen-steps-bitcoins-lead-developer

From: theymos
<theymos@mm...> -
2010-09-08 16:28:44

Someone on IRC said that they'd like to be notified of new versions through a mailing list, so I thought I'd start reposting Satoshi's version announcements here. Hopefully no one finds this annoying...

http://www.bitcoin.org/smf/index.php?topic=999.0

Version 0.3.12 is now available.

Features:
- json-rpc errors return a more standard error object. (thanks to Gavin Andresen)
- json-rpc command line returns exit codes.
- json-rpc "backupwallet" command.
- Recovers and continues if an exception is caused by a message you received. Other nodes shouldn't be able to cause an exception, and it hasn't happened before, but if a way is found to cause an exception, this would keep it from being used to stop network nodes.

If you have json-rpc code that checks the contents of the error string, you need to change it to expect error objects of the form {"code":<number>,"message":<string>}, which is the standard. See this thread:
http://www.bitcoin.org/smf/index.php?topic=969.0

Download:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.12/

https://sourceforge.net/p/bitcoin/mailman/bitcoin-list/?viewmonth=201008

From: theymos
<theymos@mm...> -
2010-10-21 18:02:23

http://www.bitcoin.org/smf/index.php?topic=1528.0

Version 0.3.14 is now available
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.14/

Changes:
- Key pool feature for safer wallet backup
Gavin Andresen:
- TEST network mode with switch -testnet
- Option to use SSL for JSON-RPC connections on unix/osx
- validateaddress RPC command
eurekafag:
- Russian translation

---

More info about the key pool feature:
http://www.bitcoin.org/smf/index.php?topic=1414.0
Now you only have to back up after every 100 sends, new addresses, generations, or transactions received by IP address.

More info about RPC SSL:
http://www.bitcoin.org/wiki/doku.php?id=rpcssl

https://sourceforge.net/p/bitcoin/mailman/bitcoin-list/?viewmonth=201010

From: Satoshi Nakamoto
<satoshin@gm...> -
2010-12-08 23:11:55

Version 0.3.18 is now available.

Changes:
- Fixed a wallet.dat compatibility problem if you downgraded from 0.3.17
and then upgraded again
- IsStandard() check to only include known transaction types in blocks
- Jgarzik's optimisation to speed up the initial block download a little

The main addition in this release is the Accounts-based JSON-RPC
commands that Gavin's been working on (more details at
http://www.bitcoin.org/smf/index.php?topic=1886.0).
- getaccountaddress
- sendfrom
- move
- getbalance
- listtransactions

https://sourceforge.net/p/bitcoin/mailman/bitcoin-list/?viewmonth=201011

From: Gavin Andresen
<gavinandresen@gm...> -
2011-02-23 01:22:25

Binaries for Bitcoin version 0.3.20.01 are available at:
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.20/

There were several changes and additions to the JSON
remote-procedure-call interface;
there are no significant user interface changes. See:
http://www.bitcoin.org/smf/index.php?topic=3473.msg48839#msg48839
... for details.

This version does fix one significant denial-of-service attack
(earlier versions of
bitcoin could be caused to crash due to running out of memory by a remote
attacker).

SHA1-checksums for the binary files are:
7dfbc05b36112f59886a29f044cfd21c6c253169 bitcoin-0.3.20.01-linux.tar.gz

3fe4c5f2a5406322a2f116b30aefbd402b079940 bitcoin-0.3.20.01-win32-setup.exe

dffb709a90a7abcff08c2ef1e79d3f9b54751786 bitcoin-0.3.20.01-win32.zip

b540825d864e7561cc21465ad072fb299e0d817a bitcoin-0.3.20.01-macosx.zip

Gavin Andresen gavinandresen@...


https://sourceforge.net/p/bitcoin/mailman/bitcoin-list/?viewmonth=201102

From: Gavin Andresen
<gavinandresen@gm...> -
2011-09-23 16:31:38

Bitcoin version 0.4.0 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/

The main feature in this release is wallet private key encryption;
you can set a passphrase that must be entered before sending coins.
See below for more information; if you decide to encrypt your wallet,
WRITE DOWN YOUR PASSPHRASE AND PUT IT IN A SECURE LOCATION. If you
forget or lose your wallet passphrase, you lose your bitcoins.
Previous versions of bitcoin are unable to read encrypted wallets,
and will crash on startup if the wallet is encrypted.

Also note: bitcoin version 0.4 uses a newer version of Berkeley DB
(bdb version 4.8) than previous versions (bdb 4.7). If you upgrade
to version 0.4 and then revert back to an earlier version of bitcoin
the it may be unable to start because bdb 4.7 cannot read bdb 4.8
"log" files.


https://sourceforge.net/p/bitcoin/mailman/bitcoin-list/?viewmonth=201109

Re: [bitcoin-list]
Bitcoin-Qt and bitcoind version 0.5 released

On 21 November 2011 21:57,
Gavin Andresen
<gavinandresen@...>

wrote:

> Bitcoin version 0.5.0 is now available for download at:
> http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.0/
> The major change for this release is a completely new
> graphicalinterface that uses the Qt user interface toolkit.
> This release include German, Spanish, Spanish-Castilian, Norwegianand
> Dutch translations. More translations are welcome; join theproject at
> Transifex if you can help:
> https://www.transifex.net/projects/p/bitcoin/
> Please report bugs using the issue tracker at github:
> https://github.com/bitcoin/bitcoin/issues
> If you cannot or do not want to run Bitcoin-Qt, a bug-fix-only
> Bitcoin version 0.4.1 is also available at sourceforge.


https://sourceforge.net/p/bitcoin/mailman/bitcoin-list/?viewmonth=201111

From: Gavin Andresen
<gavinandresen@gm...> -
2012-05-14 17:10:02


CVE-2012-2459: Critical Vulnerability

A denial-of-service vulnerability that affects all versions of
bitcoind and Bitcoin-Qt has been reported and fixed. An attacker
could isolate a victim's node and cause the creation of blockchain
forks.

Because this bug could be exploited to severely disrupt the Bitcoin
network we consider this a critical vulnerability, and encourage
everybody to upgrade to the latest version: 0.6.2.

Backports for older releases (0.5.5 and 0.4.6) are also available if
you cannot upgrade to version 0.6.2.

Full technical details are being withheld to give people the
opportunity to upgrade.

Thanks to Forrest Voight for discovering and reporting the vulnerability.

https://sourceforge.net/p/bitcoin/mailman/bitcoin-list/?viewmonth=201205

From: Gavin Andresen
<gavinandresen@gm...> -
2012-05-08 23:57:21

Bitcoin version 0.6.2 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.2/

This is a bug-fix and code-cleanup release, with no major new features.

NOTABLE CHANGES
===============

Much faster shutdowns. However, the blkindex.dat file is no longer
portable to different data directories by default. If you need a
portable blkindex.dat file then run with the new -detachdb=1 option
or the "Detach databases at shutdown" GUI preference.

Fixed https://github.com/bitcoin/bitcoin/issues/1065, a bug that
could cause long-running nodes to crash.

Mac and Windows binaries are compiled against OpenSSL 1.0.1b (Linux
binaries are dynamically linked to the version of OpenSSL on the system).


Thanks to everybody who contributed to this release:

Chris Moore
Dwayne C. Litzenberger
Gavin Andresen
Jeff Garzik
Luke Dashjr
Matt Corallo
Philip Kaufmann
Pieter Wuille
R E Broadley
Timothy Redaelli
Wladimir J. van der Laan
cardpuncher
freewil
graingert
sje397

https://sourceforge.net/p/bitcoin/mailman/bitcoin-list/?viewmonth=201205

From: Gavin Andresen
<gavinandresen@gm...> -
2011-04-18 16:19:59

Hey y'all:

I put the Reason.TV folks in touch with Jerry Brito (he already knows
them); I think Jerry will be a really good person to talk about "big
picture Bitcoin" stuff. I did a Surprisingly Free podcast with him
that will be out tomorrow ( http://surprisinglyfree.com/ )

Gavin Andresen
http://clearcoin.com/

https://sourceforge.net/p/bitcoin/mailman/bitcoin-press/?viewmonth=201104

diawiki


----------------------------------------------------------
109 Consensus (hard fork)
Two million byte size limit with sigop and sighash limits
Gavin Andresen
Standard
Rejected

BIP: 109
Layer: Consensus (hard fork)
Title: Two million byte size limit with sigop and sighash limits
Author: Gavin Andresen <gavinandresen@gmail.com>
Comments-Summary: No comments yet.
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0109
Status: Rejected
Type: Standards Track
Created: 2016-01-28
License: PD
https://github.com/bitcoin/bips/blob/master/bip-0109.mediawiki
--------------------------------------------------------------


BIP: 112
Layer: Consensus (soft fork)
Title: CHECKSEQUENCEVERIFY
Author: BtcDrak <btcdrak@gmail.com>
Mark Friedenbach <mark@friedenbach.org>
Eric Lombrozo <elombrozo@gmail.com>
Comments-Summary: No comments yet.
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0112
Status: Final
Type: Standards Track
Created: 2015-08-10
License: PD
https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki

Gavin will visit the CIA
April 27, 2011, 07:00:26 PM
Merited by OgNasty (1), coolcoinz (1)
#1
I want to get this out in the open because it is the kind of thing that will generate conspiracy theories: I'm going to give a presentation about Bitcoin at CIA headquarters in June at an emerging technologies conference for the US intelligence community.

I accepted the invitation to speak because the fact that I was invited means Bitcoin is already on their radar, and I think it might be a good chance to talk about why I think Bitcoin will make the world a better place. I think the goals of this project are to create a better currency, create a more competitive and efficient international payment system, and give people more direct control over their finances. And I don't think any of those goals are incompatible with the goals of government.

I'm only very slightly worried that talking about bitcoin at the CIA will increase the chances they'll try to do something we don't want them to do. I think accepting their invitation and being open about exactly what bitcoin is will make it less likely they'll see it as a threat.

PS: Full disclosure: I'll be paid a one-time fee of $3,000 to cover expenses and pay me for my time. I don't want any "Gavin is on the CIA's payroll" rumors to get started, either...

As always, comments and questions and discussion welcome. I'd really rather not hear any conspiracy theories about how they'll secretly implant a mind-control chip in my head while I'm there, though.... https://bitcointalk.org/?topic=6652.0

Bitcoin Classic 0.11.2
@gavinandresen gavinandresen released this on 10 Feb 2016 https://github.com/bitcoinclassic/bitcoinclassic/releases/tag/v0.11.2.cl1

Long term Scalability of Bitcoin and the 1 MB block size limit
November 01, 2013, 10:07:00 AM

"Consensus is the block size limit will have to rise.
Us geeks were/will/are arguing over how and when, not if..."
Gavin Andresen


El consenso es que el límite de tamaño de bloque tendrá que aumentar.
Nosotros, los frikis, estábamos discutiendo sobre cómo y cuándo, no si ...
Gavin Andresen

https://bitcointalk.org/index.php?topic=322748.msg3455664#msg3455664

Dan Kaminsky's Blog
The Cryptographically Provable Con Man


"Yeah, what the heck?

I was as surprised by the ‘proof’ as anyone, and don’t yet know exactly what is going on.

It was a mistake to agree to publish my post before I saw his– I assumed his post would simply be a signed message anybody could easily verify.

And it was probably a mistake to even start to play the Find Satoshi game, but I DO feel grateful to Satoshi.

If I’m lending credibility to the idea that a public key operation should remain private, that is entirely accidental. OF COURSE he should just publish a signed message or (equivalently) move some btc through the key associated with an early block.

Feel free to quote or republish this email".
Gavin Andresen

https://dankaminsky.com/2016/05/03/the-cryptographically-provable-con-man/