From: Gregory Maxwell <gmaxwell@gmail•com>
To: Justus Ranvier <justusranvier@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Working on social contracts (was: Paper Currency)
Date: Mon, 19 May 2014 14:07:38 -0700 [thread overview]
Message-ID: <CAAS2fgQADU27NABcP1r52YTgDUy+PX7OZfT5H7XSsecjy1dmQg@mail.gmail.com> (raw)
In-Reply-To: <537A630D.104@localhost.local>
On Mon, May 19, 2014 at 1:01 PM, Justus Ranvier <justusranvier@gmail•com> wrote:
> YOU can make promises about YOUR future behavior. So can everyone else.
>
> The rest of the community can keep track of which developers will and
> will not make promises about what changes they will and will not
> attempt to implement in Bitcoin, and they can use that information to
> make informed decisions about which software they will choose to support.
I promise that if bad people show up with a sufficient pointy gun that
I'll do whatever they tell me to do. I'll make bad proposals, submit
backdoors, and argue with querulous folks on mailing lists, diverting
them from real development and review work, all as commanded. Maybe
I'll try to sneak out a warning of some kind, maybe... but with my
life or my families or friends lives on the line— probably not.
... and I think that anyone who tells you otherwise probably just
hasn't really thought it through. So what is the point of commitments
like that? People change, people go crazy, people are coerced. Crap
happens, justifications are made, life goes on— or so we hope.
What matters is building infrastructure— both social and technical—
that is robust against those sorts of failures. If you're depending on
individual developers (including anonymous parties and volunteers) to
be somehow made more trustworthy by some promises on a mailing list
you've already lost.
If you care about this you could instead tell us about how much time
you promise to spend reviewing technical work to make sure such
attacks cannot be successful, regardless of their origins. Where are
your gitian signatures? I think thats a lot more meaningful, and it
also improves security for everyone involved since knowing that such
attacks can not succeeded removes the motivation for ever trying.
A lot of what Bitcoin is about, for me at least, is building systems
which are as trustless as possible— ruled by unbreakable rules
embodied in the software people chose to use out of their own free
will and understanding. Or at least thats the ideal we should try to
approximate. If we're successful the adhomenim you've thrown on this
list will be completely pointless— not because people are trusted to
not do evil but because Bitcoin users won't accept technology that
makes it possible.
So please go ahead and assume I'm constantly being evil and trying to
sneak something in... the technology and security can only be better
for it, but please leave the overt attacks at the door. Think
gentleman spies, not a street fighting death match. The rude attacks
and characterizations just turn people off and don't uncover actual
attacks. Maybe the informal guideline should be one flame-out
personal attack per cryptosystem you break, serious bug you uncover,
or impossible problem you solve. :)
next prev parent reply other threads:[~2014-05-19 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 19:41 Gavin Andresen
2014-05-19 20:01 ` Justus Ranvier
2014-05-19 20:06 ` Gavin Andresen
2014-05-19 20:06 ` Mike Hearn
2014-05-19 20:13 ` Justus Ranvier
2014-05-19 21:07 ` Gregory Maxwell [this message]
2014-05-19 21:18 ` Justus Ranvier
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=CAAS2fgQADU27NABcP1r52YTgDUy+PX7OZfT5H7XSsecjy1dmQg@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=justusranvier@gmail$(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