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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UFrNU-0006Xz-5I for bitcoin-development@lists.sourceforge.net; Wed, 13 Mar 2013 19:30:20 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gnomon.org.uk designates 93.93.131.22 as permitted sender) client-ip=93.93.131.22; envelope-from=roy@gnomon.org.uk; helo=darla.gnomon.org.uk; Received: from darla.gnomon.org.uk ([93.93.131.22]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1UFrNR-0006xy-Ce for bitcoin-development@lists.sourceforge.net; Wed, 13 Mar 2013 19:30:20 +0000 Received: from darla.gnomon.org.uk (localhost.gnomon.org.uk [127.0.0.1]) by darla.gnomon.org.uk (8.14.3/8.14.3) with ESMTP id r2DJTq0i042292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 13 Mar 2013 19:29:58 GMT (envelope-from roy@darla.gnomon.org.uk) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.95.3 at darla.gnomon.org.uk Received: (from roy@localhost) by darla.gnomon.org.uk (8.14.3/8.14.1/Submit) id r2DJTqBB042291; Wed, 13 Mar 2013 19:29:52 GMT (envelope-from roy) Date: Wed, 13 Mar 2013 19:29:52 +0000 From: Roy Badami To: Pieter Wuille Message-ID: <20130313192951.GP96148@giles.gnomon.org.uk> References: <20130313174838.GA22621@savin> <2FCCE0F7-66B0-4EBE-8448-C5F0F92A75FF@ceptacle.com> <20130313182805.GA7921@vps7135.xlshosting.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130313182805.GA7921@vps7135.xlshosting.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -3.9 (---) 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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -2.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1UFrNR-0006xy-Ce Cc: bitcoin-development@lists.sourceforge.net, Michael Gronager Subject: Re: [Bitcoin-development] Blocksize and off-chain transactions 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: Wed, 13 Mar 2013 19:30:20 -0000 On Wed, Mar 13, 2013 at 07:28:06PM +0100, Pieter Wuille wrote: > IMHO, the way to go is first get a 0.8.1 out that mimics the old > behaviour - just as a stopgap solution. Presumably not emulate too precisely, at least if your initial report that the block caused 0.7 to 'get stuck' was correct. A network that has a mix of 0.8.1 nodes (which will reject the block) and 0.7 nodes (which will hang when receiving the block?) would appear to remove the fork risk. Is it obvious that no other serious problems remain in such a network? (Although I note your proposal to patch 0.7 too, so hopefully the network wouldn't remain in that state for very long) roy