Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1TuopK-0002Bm-Gb
	for bitcoin-development@lists.sourceforge.net;
	Mon, 14 Jan 2013 18:32:06 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.172 as permitted sender)
	client-ip=209.85.212.172; envelope-from=gavinandresen@gmail.com;
	helo=mail-wi0-f172.google.com; 
Received: from mail-wi0-f172.google.com ([209.85.212.172])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1TuopJ-0003B5-VW
	for bitcoin-development@lists.sourceforge.net;
	Mon, 14 Jan 2013 18:32:06 +0000
Received: by mail-wi0-f172.google.com with SMTP id o1so1503693wic.5
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 14 Jan 2013 10:31:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.78.162 with SMTP id c2mr136273634wjx.46.1358188319876;
	Mon, 14 Jan 2013 10:31:59 -0800 (PST)
Received: by 10.194.176.164 with HTTP; Mon, 14 Jan 2013 10:31:59 -0800 (PST)
In-Reply-To: <CA+8xBpdV5SNDBU=y07qPcvPksWOQ35uHpsSopAVRQX-xU=o6-Q@mail.gmail.com>
References: <20130114104447.GA15854@savin>
	<CA+8xBpdV5SNDBU=y07qPcvPksWOQ35uHpsSopAVRQX-xU=o6-Q@mail.gmail.com>
Date: Mon, 14 Jan 2013 13:31:59 -0500
Message-ID: <CABsx9T3FpVq-m8P=ZbFmsJMni-4g0y4+hQ+hqy2gUKi84jw9DQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gavinandresen[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1TuopJ-0003B5-VW
Subject: Re: [Bitcoin-development] Proposal: make the private key for
 testnet genesis block public
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 18:32:06 -0000

The testnet3 genesis block is identical to the main network genesis
block, except it has a different timestamp and nonce.

So its coinbase pays to the same public key as the main network. I
don't have that private key.

Good idea for testnet4, whenever that happens, though.

-- 
--
Gavin Andresen