From: Mark Friedenbach <mark@friedenbach•org>
To: ZmnSCPxj <ZmnSCPxj@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Scott Roberts <zawy@yahoo•com>
Subject: Re: [bitcoin-dev] New difficulty algorithm part 2
Date: Thu, 12 Oct 2017 08:25:23 -0700 [thread overview]
Message-ID: <8369AFB5-05BF-4483-A81D-82ED34B4A22F@friedenbach.org> (raw)
In-Reply-To: <NzOnTr-caLMhcX_xk64TLPkbu75N79WmAl3P9e2jOo5mCOFg9G3SIxgj6FXxo4Euau3h4u_iJe04NERnBpw8D_08ZwzbUQcjTCJMR663oOI=@protonmail.com>
> On Oct 12, 2017, at 3:40 AM, ZmnSCPxj via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> As most Core developers hodl vast amounts, it is far more likely that any hardfork that goes against what Core wishes will collapse, simply by Core developers acting in their capacity as hodlers of Bitcoin, without needing to do any special action in their capacity as developers.
While this might be true of some, it is most certainly not true of many, and it is a very dangerous men to the safety and well being of people on this list.
You don’t get bitcoin for being a bitcoin developer, and there is no reason to suppose a developer has any more or less bitcoin than anyone else in the industry.
It is certainly the case that a large number of people and organizations who are not developers hold massive amounts of bitcoin (hundred of thousands each, millions in aggregate).
next prev parent reply other threads:[~2017-10-12 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1664384101.5473696.1507733420536.ref@mail.yahoo.com>
2017-10-11 14:50 ` Scott Roberts
2017-10-12 10:40 ` ZmnSCPxj
2017-10-12 15:25 ` Mark Friedenbach [this message]
2017-10-12 15:42 Scott Roberts
2017-10-13 4:45 ` ZmnSCPxj
2017-10-13 11:35 ` Scott Roberts
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=8369AFB5-05BF-4483-A81D-82ED34B4A22F@friedenbach.org \
--to=mark@friedenbach$(echo .)org \
--cc=ZmnSCPxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=zawy@yahoo$(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