Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <jgarzik@exmulti.com>) id 1QwIZS-0001TE-OB for bitcoin-development@lists.sourceforge.net; Wed, 24 Aug 2011 18:53:02 +0000 X-ACL-Warn: Received: from mail-iy0-f171.google.com ([209.85.210.171]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QwIZR-0007BE-RL for bitcoin-development@lists.sourceforge.net; Wed, 24 Aug 2011 18:53:02 +0000 Received: by iyf13 with SMTP id 13so2700329iyf.30 for <bitcoin-development@lists.sourceforge.net>; Wed, 24 Aug 2011 11:52:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.244.202 with SMTP id lr10mr4848107icb.227.1314211558879; Wed, 24 Aug 2011 11:45:58 -0700 (PDT) Received: by 10.43.50.200 with HTTP; Wed, 24 Aug 2011 11:45:58 -0700 (PDT) X-Originating-IP: [99.43.178.25] In-Reply-To: <CABsx9T12R2dd=Ak7k4N+ZVAyLvJnx9oS0vVjwRa5T+UoCjbEMQ@mail.gmail.com> References: <CABsx9T1uw43JuvhEmJP0KCyojsDi1r7v6BaLBHz7wWazduE5iw@mail.gmail.com> <201108241215.36847.luke@dashjr.org> <CAAS2fgQspsXy1Vw=fNr1FvsDRkEbP6dEcFLgUpK9DrBKXyiWNg@mail.gmail.com> <CAJ1JLtsxPG9v-Hwdb-pfgY6GU0Z4it+frFzw_tObVbNC6Xgdjw@mail.gmail.com> <CAAS2fgTARAMqMu79Sp4XS4KxmUBWiXebpavHWr-EdLZbxS=sTw@mail.gmail.com> <CAJ1JLttqEnCjALadESmpntxSobD8Lj1zcXL4S7ghqdhyBrwVNw@mail.gmail.com> <CABsx9T12R2dd=Ak7k4N+ZVAyLvJnx9oS0vVjwRa5T+UoCjbEMQ@mail.gmail.com> Date: Wed, 24 Aug 2011 14:45:58 -0400 Message-ID: <CA+8xBpefWGE02SWRe=6GdNKc1jwdDQu-HEvDiEF_pw2XLX_7rQ@mail.gmail.com> From: Jeff Garzik <jgarzik@exmulti.com> To: Gavin Andresen <gavinandresen@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1QwIZR-0007BE-RL Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] New standard transaction types: time to schedule a blockchain split? 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: Wed, 24 Aug 2011 18:53:02 -0000 On Wed, Aug 24, 2011 at 1:57 PM, Gavin Andresen <gavinandresen@gmail.com> w= rote: > This discussion is convincing me that scheduling a blockchain split is > definitely the wrong idea at this time. =A0We can revisit in N months, Strongly agreed... --=20 Jeff Garzik exMULTI, Inc. jgarzik@exmulti.com