From: Felipe Micaroni Lalli <micaroni@walltime•info>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core versus XT observations
Date: Wed, 19 Aug 2015 14:14:52 -0300 [thread overview]
Message-ID: <55D4B98C.1030903@walltime.info> (raw)
In-Reply-To: <CAKujSOHGPTy-A3TUKKxO4kJYhWaReqyni2aE0CvK0ON8tixNNw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
On 19/08/2015 09:24, Ken Friece via bitcoin-dev wrote:
> 5.) Not-BitcoinXT is a really terrible idea. Mike has proven time and time
> again that he will not blink or back down. The chances of Not-BitcoinXT
> gaining 25% of the hashrate are pretty much nil, so in effect, all
> Not-BitcoinXT will do is help XT reach the 75% threshold sooner and end up
> putting more people on the losing side of the fork.
If 25% or more of the hashpower are against XT, Not-BitcoinXT becomes an
important weapon for them. This was not a "bad idea", but can shake the
market.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-08-19 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 12:24 Ken Friece
2015-08-19 13:05 ` Milly Bitcoin
2015-08-19 17:14 ` Felipe Micaroni Lalli [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=55D4B98C.1030903@walltime.info \
--to=micaroni@walltime$(echo .)info \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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