--- layout: default title: 'Re: Bitcoin v0.1 released' date: 2009-01-12 18:52:45 grand_parent: Emails parent: Dustin Trammel nav_order: 1 --- # Re: Bitcoin v0.1 released The email on the Cryptography Mailing List that announced Bitcoin publicly to the world. {: .fs-6 .fw-300 } --- ``` From satoshi@vistomail.com Mon Jan 12 18:52:45 2009 Return-Path: Delivered-To: dustintrammell-dtrammell@dustintrammell.com Received: (qmail 18309 invoked from network); 12 Jan 2009 18:52:45 -0000 Received: from anonymousspeech.com (HELO mail.anonymousspeech.com) (124.217.253.42) by oaklabs.net with SMTP; 12 Jan 2009 18:52:45 -0000 Received: from server123 ([124.217.253.42]) by anonymousspeech.com with MailEnable ESMTP; Tue, 13 Jan 2009 02:42:42 +0800 MIME-Version: 1.0 Date: Tue, 13 Jan 2009 02:33:28 +0800 X-Mailer: Chilkat Software Inc (http://www.chilkatsoft.com) X-Priority: 3 (Normal) Subject: Re: Bitcoin v0.1 released Content-Type: text/plain From: "Satoshi Nakamoto" Reply-To: satoshi@vistomail.com To: dtrammell@dustintrammell.com Message-ID: X-Evolution-Source: pop://dustintrammell-dtrammell@mail.oaklabs.net/ Content-Transfer-Encoding: 8bit > I'm currently reading through your paper. At the timestamp server > section you mention newspapers and usenet, so I thought you might be > interested in this if you have not seen it already: > > http://www.publictimestamp.org/ Thanks, I hadn't seen that yet. It looks very well presented. There was an older one that's been running for a long time that publishes its hashes to Usenet. I'm surprised this one isn't using Usenet, although it is kind of difficult to get access to post to Usenet in an automated way these days. If they can get a magazine or newspaper to publish their hashes, it would work a lot easier in court for their purposes. Bitcoin and all timestamp servers share the basic functionality of periodically collecting things into blocks and hashing them into a chain. > By the way, I'm also currently running the alpha code on one of my > workstations. So far it has two "Generated" messages, however the > "Credit" field for those is 0.00 and the balance hasn't changed. Is > this due to the age/maturity requirement for a coin to be valid? Right, the credit field stays 0.00 until it matures, then it'll be 50.00. Do you think it would be clearer if I left the credit field blank until it matures? I should put some text in the transaction details (when you double click on it) explaining how it works. (was it obvious you can doubleclick on a line for details?) Be sure to upgrade to v0.1.3 if you haven't already. This version has really stabilized things. ```