From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UFOi3-0004tL-Ow for bitcoin-development@lists.sourceforge.net; Tue, 12 Mar 2013 12:53:39 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of outlook.com designates 65.55.111.160 as permitted sender) client-ip=65.55.111.160; envelope-from=jayf@outlook.com; helo=blu0-omc4-s21.blu0.hotmail.com; Received: from blu0-omc4-s21.blu0.hotmail.com ([65.55.111.160]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UFOi1-0007Is-I4 for bitcoin-development@lists.sourceforge.net; Tue, 12 Mar 2013 12:53:39 +0000 Received: from BLU0-SMTP421 ([65.55.111.137]) by blu0-omc4-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 12 Mar 2013 05:41:02 -0700 X-EIP: [ACPMlK+m67RnE17Ex5DsfIHKI1NtOrI/] X-Originating-Email: [jayf@outlook.com] Message-ID: Received: from [192.168.1.15] ([67.189.14.219]) by BLU0-SMTP421.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 12 Mar 2013 05:41:01 -0700 Date: Tue, 12 Mar 2013 05:40:59 -0700 From: Jay F User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Jorge_Tim=F3n?= References: <20130312114426.GA3701@vps7135.xlshosting.net> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 12 Mar 2013 12:41:01.0409 (UTC) FILETIME=[DA689510:01CE1F1E] X-Spam-Score: -1.5 (-) 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 (jayf[at]outlook.com) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [65.55.111.160 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 MSGID_FROM_MTA_HEADER Message-Id was added by a relay X-Headers-End: 1UFOi1-0007Is-I4 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Warning: many 0.7 nodes break on large number of tx/block; fork risk X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 12:53:40 -0000 On 3/12/2013 5:18 AM=2C Jorge Tim=F3n wrote: > A related question...some people mentioned yesterday on #bitcoin-dev > that 0.5 appeared to be compatible with 0.8. > Was that only for the "fatal block" and would have forked 0.8 later > too or is it something else? > I'm having a hard time understanding this 0.5 thing=2C if someone can > bring some light to it I would appreciate it. > > Thanks in advance > It was reported that not all 0.7 died from the BDB error either. This=20 will likely take a post-mortem to determine exactly what build=20 environments and versions are incompatible=2C by feeding each the bloated=20 block (hopefully there are lots of snapshots of the bad chain being the=20 best height for testing=3B I forgot to get one).