From: Matt Corallo <lf-lists@mattcorallo.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin XT 0.11A
Date: Mon, 17 Aug 2015 21:42:29 +0000 [thread overview]
Message-ID: <55D25545.3030406@mattcorallo.com> (raw)
In-Reply-To: <CAEX2NSfaPv0g07hfT31voGWX05Z6uaBsZOjhMkOwBr4mdHbPQw@mail.gmail.com>
On 08/16/15 23:22, Andrew LeCody via bitcoin-dev wrote:
> Cam, your scenario makes no sense.
>
>> 1. Spoil the ballot. Have Bitcoin Core propagate the Bitcoin XT version
> string.
>> 2. Encourage all miners to false vote for the Bitcoin XT fork.
>
> This would obliterate any confidence in Bitcoin Core. I seriously doubt
> anyone would actually be ok with a pull request implementing this.
Bitcoin Core doesnt have to do this. It is rational if you have >25% of
hash power (or if you believe 25% of hash power is doing this) to do this.
If a 75% hardfork target is reached, and >25% of the hashpower doesnt
allow the hardfork, and the hardfork is strictly more permissive than
the original (ie it is essentially a reverse softfork - there are no
previously valid blocks which are not still valid), then the miners who
voted for the fork would be constantly generating blocks which are
soft-forked-out by the >25% and non-supporting miners.
I believe this was pointed out to the Bitcoin XT folks weeks ago, but
apparently did not sway the decision to use 75% and a (as far as I can
tell?) strictly more permissive hardfork.
Matt
next prev parent reply other threads:[~2015-08-17 21:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 22:39 [bitcoin-dev] Bitcoin XT 0.11A muyuubyou
2015-08-16 18:37 ` Andrew LeCody
2015-08-16 23:02 ` Cameron Garnham
2015-08-16 23:22 ` Andrew LeCody
2015-08-17 0:03 ` Cameron Garnham
2015-08-17 6:42 ` Peter Todd
2015-08-17 12:29 ` Andrew LeCody
2015-08-17 12:33 ` Eric Lombrozo
2015-08-19 10:09 ` Jorge Timón
2015-08-19 15:41 ` s7r
2015-08-19 22:28 ` Jorge Timón
2015-08-19 22:45 ` Adam Back
2015-08-19 23:23 ` Peter Todd
2015-08-20 10:25 ` s7r
2015-08-20 11:32 ` Milly Bitcoin
2015-08-20 11:46 ` Hector Chu
2015-08-20 12:29 ` Milly Bitcoin
2015-08-20 14:25 ` Tamas Blummer
2015-08-17 21:42 ` Matt Corallo [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-16 2:08 muyuubyou
2015-08-15 17:02 Mike Hearn
2015-08-15 17:57 ` s7r
2015-08-15 18:38 ` s7r
2015-08-15 19:21 ` Mike Hearn
2015-08-15 20:36 ` Milly Bitcoin
2015-08-15 20:47 ` Bryan Bishop
2015-08-15 21:10 ` Milly Bitcoin
2015-08-15 20:55 ` Micha Bailey
2015-08-15 21:32 ` Eric Lombrozo
2015-08-15 22:01 ` Ken Friece
2015-08-15 22:16 ` Eric Lombrozo
2015-08-15 22:27 ` Angel Leon
2015-08-15 22:28 ` Ken Friece
2015-08-15 22:55 ` Mark Friedenbach
2015-08-15 23:04 ` Ken Friece
2015-08-15 23:07 ` Eric Lombrozo
2015-08-15 23:30 ` Michael Naber
2015-08-15 23:40 ` Mark Friedenbach
2015-08-15 23:57 ` Ken Friece
2015-08-16 0:06 ` Milly Bitcoin
2015-08-16 13:49 ` Mike Hearn
2015-08-16 15:44 ` Anthony Towns
2015-08-16 16:07 ` Tamas Blummer
2015-08-16 16:12 ` Levin Keller
2015-08-16 17:01 ` Adam Back
2015-08-16 18:15 ` Tamas Blummer
2015-08-16 20:27 ` Eric Voskuil
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=55D25545.3030406@mattcorallo.com \
--to=lf-lists@mattcorallo.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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