Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <gmaxwell@gmail.com>) id 1Rt0kA-0008VS-2b for bitcoin-development@lists.sourceforge.net; Thu, 02 Feb 2012 17:46:46 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.47 as permitted sender) client-ip=209.85.212.47; envelope-from=gmaxwell@gmail.com; helo=mail-vw0-f47.google.com; Received: from mail-vw0-f47.google.com ([209.85.212.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Rt0k6-0004xL-Ad for bitcoin-development@lists.sourceforge.net; Thu, 02 Feb 2012 17:46:45 +0000 Received: by vbbff1 with SMTP id ff1so2712469vbb.34 for <bitcoin-development@lists.sourceforge.net>; Thu, 02 Feb 2012 09:46:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.91.200 with SMTP id cg8mr1576383vdb.65.1328204796865; Thu, 02 Feb 2012 09:46:36 -0800 (PST) Received: by 10.220.151.200 with HTTP; Thu, 2 Feb 2012 09:46:36 -0800 (PST) In-Reply-To: <CAAS2fgQsJjKy7XakOaQ7vqf2ewD0JJ-1MEbNvj_r2K0E8kWkww@mail.gmail.com> References: <D55C3D18-8286-44E9-B877-6FCE7C05E980@ceptacle.com> <CAAS2fgSQZ1wv=OXnBnGbKnLTZXbn909umpPBaZDF2g6vy8katA@mail.gmail.com> <CAAS2fgR_r=NpFJJEQ=canx5noUeQDyJPYRJ4D5rzCGC_qLOgEg@mail.gmail.com> <CAAS2fgQsJjKy7XakOaQ7vqf2ewD0JJ-1MEbNvj_r2K0E8kWkww@mail.gmail.com> Date: Thu, 2 Feb 2012 12:46:36 -0500 Message-ID: <CAAS2fgRe9-vaT0+xR_V1d68h=zPb59TZuGniqW1RNQRFUFbbYw@mail.gmail.com> From: Gregory Maxwell <gmaxwell@gmail.com> To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 (gmaxwell[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 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Rt0k6-0004xL-Ad Subject: Re: [Bitcoin-development] Announcement: libcoin 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: Thu, 02 Feb 2012 17:46:46 -0000 On Thu, Feb 2, 2012 at 12:36 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote= : > On Thu, Feb 2, 2012 at 12:12 PM, Gregory Maxwell <gmaxwell@gmail.com> wro= te: >> sync, libbitcoin only made it to height 138k (of course, because the >> time is mostly spent late in the chain 138k is not very far along=E2=80= =94 I'm >> guessing it's going to take libbitcoin 3x-4x longer all said) > > It ended up taking almost exactly twice as long, FWIW. (and Gah: forgive the autocompletion of my fingers: I'm apparently unable to type the word coin without prefacing it with bit) *libcoin* not libbitcoin.