From: Jay F <jayf@outlook•com>
To: "Jorge Timón" <jtimonmv@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Warning: many 0.7 nodes break on large number of tx/block; fork risk
Date: Tue, 12 Mar 2013 05:40:59 -0700 [thread overview]
Message-ID: <BLU0-SMTP421E184DD5F1D5562F40D3FC8E20@phx.gbl> (raw)
In-Reply-To: <CABOyFfrVCRfJ2R8a-XGcviSbORDswe+N13G_FrVkbWtEhtoTjw@mail.gmail.com>
On 3/12/2013 5:18 AM, Jorge Timón 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, 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
will likely take a post-mortem to determine exactly what build
environments and versions are incompatible, by feeding each the bloated
block (hopefully there are lots of snapshots of the bad chain being the
best height for testing; I forgot to get one).
next prev parent reply other threads:[~2013-03-12 12:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 0:18 Pieter Wuille
2013-03-12 1:01 ` Pieter Wuille
2013-03-12 9:10 ` Mike Hearn
2013-03-12 9:53 ` Jorge Timón
2013-03-12 9:57 ` Peter Todd
2013-03-12 10:10 ` Mike Hearn
2013-03-12 10:17 ` Peter Todd
2013-03-12 10:13 ` Michael Gronager
2013-03-12 10:26 ` Peter Todd
2013-03-12 10:43 ` Mike Hearn
2013-03-12 10:40 ` Roy Badami
2013-03-12 11:44 ` Pieter Wuille
2013-03-12 12:11 ` Mike Hearn
2013-03-12 12:27 ` Michael Gronager
2013-03-12 12:18 ` Jorge Timón
2013-03-12 12:40 ` Jay F [this message]
2013-03-12 12:38 ` Gregory Maxwell
2013-03-12 13:00 ` 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=BLU0-SMTP421E184DD5F1D5562F40D3FC8E20@phx.gbl \
--to=jayf@outlook$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jtimonmv@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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