From: <jl2012@xbt•hk>
To: "'Matt Corallo'" <lf-lists@mattcorallo•com>,
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] A roadmap to a better header format and bigger block size
Date: Wed, 10 Feb 2016 12:26:03 +0800 [thread overview]
Message-ID: <23ab01d163bb$28e140a0$7aa3c1e0$@xbt.hk> (raw)
In-Reply-To: <56BA64F3.2060900@mattcorallo.com>
I am actually suggesting 1 hardfork, not 2. However, different rules are
activated at different time to enhance safety and reduce disruption. The
advantage is people are required to upgrade once, not twice. Any clients
designed for stage 2 should also be ready for stage 3.
-----Original Message-----
From: Matt Corallo [mailto:lf-lists@mattcorallo•com]
Sent: Wednesday, 10 February, 2016 06:15
To: jl2012@xbt•hk; bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] A roadmap to a better header format and bigger
block size
As for your stages idea, I generally like the idea (and mentioned it may be
a good idea in my proposal), but am worried about scheduling two hard-forks
at once....Lets do our first hard-fork first with the things we think we
will need anytime in the visible future that we have reasonable designs for
now, and talk about a second one after we've seen what did/didnt blow up
with the first one.
Anyway, this generally seems reasonable - it looks like most of this matches
up with what I said more specifically in my mail yesterday, with the
addition of timewarp fixes, which we should probably add, and Luke's header
changes, which I need to spend some more time thinking about.
Matt
prev parent reply other threads:[~2016-02-10 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 14:16 jl2012
2016-02-09 15:53 ` Ricardo Filipe
2016-02-09 22:15 ` Matt Corallo
2016-02-10 4:26 ` jl2012 [this message]
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='23ab01d163bb$28e140a0$7aa3c1e0$@xbt.hk' \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lf-lists@mattcorallo$(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