From: Tom Harding <tomh@thinlink•com>
To: Mike Hearn <mike@plan99•net>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] improving development model (Re: Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers
Date: Fri, 19 Jun 2015 19:59:25 -0700 [thread overview]
Message-ID: <5584D70D.2030104@thinlink.com> (raw)
In-Reply-To: <CANEZrP2iGUnU+BKzYOzNZJUPNOU_5d4oU8JRgGLS1iPtz-uRWA@mail.gmail.com>
On 6/19/2015 6:43 AM, Mike Hearn wrote:
> No surprise, the position of Blockstream employees is that hard forks
> must never happen and that everyone's ordinary transactions should go
> via some new network that doesn't yet exist.
If my company were working on spiffy new ideas that required a hard fork
to implement, I'd be rather dismayed to see the blocksize hard fork
happen *before those ideas were ready*.
Because then I'd eventually have to convince people that those ideas
were worth a hard fork all on their own. It would be much easier to
convince people to roll them in with the already necessary blocksize
hard fork, if that event could be delayed.
As far as I know, Blockstream representatives have never said that
waiting for other changes to be ready is a reason to delay the blocksize
hard fork. So if this were the real reason, it would suggest they have
been hiding their true motives for making such a fuss about the
blocksize issue.
I've got no evidence at all to support thoughts like this... just the
paranoid mindset that seems to infect a person who gets involved in
bitcoin. But the question is every bit as valid as Adam's query into
your motives.
next prev parent reply other threads:[~2015-06-20 2:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 9:22 Dr Adam Back
2015-06-19 10:45 ` Dr Adam Back
2015-06-19 11:35 ` Bryan Bishop
2015-06-19 12:02 ` Eric Lombrozo
2015-06-19 12:02 ` Eric Lombrozo
2015-06-19 12:48 ` Marcel Jamin
2015-06-19 12:49 ` Eric Lombrozo
2015-06-19 13:43 ` Mike Hearn
2015-06-20 2:59 ` Tom Harding [this message]
2015-06-19 16:05 ` Milly Bitcoin
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=5584D70D.2030104@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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