From: jl2012@xbt.hk
To: Michael Ruddy <mruddybtc@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP draft: Hardfork bit
Date: Mon, 03 Aug 2015 04:54:27 -0400 [thread overview]
Message-ID: <a09a6c8f6a2ade5545b499882aa6e2a1@xbt.hk> (raw)
In-Reply-To: <CABFP+yOd2ssjuBW3VQPYMCVepeVSMZp3C7w3-fkPW1pmGChAWA@mail.gmail.com>
I have put it on the github:
https://github.com/jl2012/bips/blob/master/hardforkbit.mediawiki
I removed the specification of coinbase message to make it simpler.
Instead, it requires that a flag block must not be shared by multiple
hardfork proposals.
I'm not sure whether it is a Standard, Informational, or Process BIP
I'm also thinking whether we should call it "hardfork bit", "hardfork
flag", or with other name.
Michael Ruddy 於 2015-08-02 06:53 寫到:
> I think your "hardfork bit" proposal is clever.
> It addresses the particular valid concern of re-org facing users of a
> fork that a small/near/fluctuating majority, or less, of mining power
> supported.
> While the "economic majority" argument may be enough on its own in
> that case, it still has some aspect of being a hand wave.
> This proposal adds support to those economic actors, which makes it
> easier for them to switch if/when they choose. That is, it provides a
> good fallback mechanism that allows them to make a decision and say,
> "we're doing this".
> Do you have the latest version up on github, or someplace where it
> would be easier to collaborate on the specific text?
next prev parent reply other threads:[~2015-08-03 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 16:23 [bitcoin-dev] BIP draft: Hardfork bit jl2012
2015-07-23 17:59 ` Tier Nolan
2015-07-23 19:26 ` jl2012
2015-08-01 13:05 ` Michael Ruddy
2015-08-01 20:23 ` jl2012
2015-08-02 10:53 ` Michael Ruddy
2015-08-03 8:54 ` jl2012 [this message]
2015-07-24 1:17 ` Gareth Williams
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=a09a6c8f6a2ade5545b499882aa6e2a1@xbt.hk \
--to=jl2012@xbt.hk \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=mruddybtc@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