From: "Eric Lombrozo" <elombrozo@gmail.com>
To: "Gregory Maxwell" <gmaxwell@gmail.com>,
"Rusty Russell" <rusty@rustcorp.com.au>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
Pieter Wuille <pieter.wuille@gmail.com>
Subject: Re: [bitcoin-dev] Versionbits BIP (009) minor revision proposal.
Date: Wed, 30 Sep 2015 05:09:51 +0000 [thread overview]
Message-ID: <em0a6ae99c-b1d5-450f-ab2e-ad085991b9ff@platinum> (raw)
In-Reply-To: <ema32ec38f-3384-48e2-9ab3-6064e4c73bde@platinum>
>While I would like to get some form of explicit acknowledgment from
>miners that a new rule is in effect, the truth of the matter is we
>still lack a means to determine whether or not miners are actually
>enforcing these rules...unless someone happens to mine a block that
>breaks the new rule. This is a bit frustrating...but that's just how it
>is.
>
I should add that hard forks do provide us with a means to determine
whether or not miners are enforcing the new rules...but generally
speaking they risk far greater disruption if anything fails to go as
planned. Between the risk of clients accepting an occasional invalid
"confirmation" or two and the risk of a total network partition, the
former seems far less serious. I believe the concerns regarding old
clients can be remedied to a very large extent by means of a good
awareness campaign.
- Eric
next prev parent reply other threads:[~2015-09-30 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 2:30 [bitcoin-dev] Versionbits BIP (009) minor revision proposal Rusty Russell
2015-09-30 2:57 ` Gregory Maxwell
2015-09-30 4:46 ` Eric Lombrozo
2015-09-30 5:09 ` Eric Lombrozo [this message]
2015-10-01 0:26 ` Rusty Russell
2015-10-01 2:54 ` Eric Lombrozo
2015-10-02 1:22 ` Rusty Russell
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=em0a6ae99c-b1d5-450f-ab2e-ad085991b9ff@platinum \
--to=elombrozo@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=gmaxwell@gmail.com \
--cc=pieter.wuille@gmail.com \
--cc=rusty@rustcorp.com.au \
/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