public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Roy Badami <roy@gnomon.org.uk>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net,
	Michael Gronager <gronager@ceptacle.com>
Subject: Re: [Bitcoin-development] Blocksize and off-chain transactions
Date: Wed, 13 Mar 2013 19:29:52 +0000	[thread overview]
Message-ID: <20130313192951.GP96148@giles.gnomon.org.uk> (raw)
In-Reply-To: <20130313182805.GA7921@vps7135.xlshosting.net>

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



  reply	other threads:[~2013-03-13 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 17:01 [Bitcoin-development] Blocksize and off-chain transactions Gavin Andresen
2013-03-13 17:48 ` Peter Todd
2013-03-13 18:01   ` Michael Gronager
2013-03-13 18:08     ` Luke-Jr
2013-03-13 18:28     ` Pieter Wuille
2013-03-13 19:29       ` Roy Badami [this message]
2013-03-13 19:43       ` Stephen Pair
2013-03-13 20:14       ` Michael Gronager

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130313192951.GP96148@giles.gnomon.org.uk \
    --to=roy@gnomon.org.uk \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gronager@ceptacle.com \
    --cc=pieter.wuille@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox