From: Jeff Garzik <jgarzik@bitpay.com>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Does anyone have anything at all signed by Satoshi's PGP key?
Date: Sat, 13 Sep 2014 10:03:20 -0400 [thread overview]
Message-ID: <CAJHLa0MaE3Ki5Hs4Tu4dQNBW-EL-857N2kf-fVxYcXM6OO-84w@mail.gmail.com> (raw)
In-Reply-To: <20140913135528.GC6333@muck>
That claim is horse manure :) He never signed private emails sent to
me, nor the forum posts.
He -might- have signed the occasional thing related to releases, I'm not sure.
On Sat, Sep 13, 2014 at 9:55 AM, Peter Todd <pete@petertodd.org> wrote:
> So far I have zero evidence that the common claim that "Satoshi PGP
> signed everything" was true; I have no evidence he ever
> cryptographically signed any communications at all.
>
> --
> 'peter'[:-1]@petertodd.org
> 00000000000000000ce4f740fb700bb8a9ed859ac96ac9871567a20fca07f76a
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-09-13 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 13:55 [Bitcoin-development] Does anyone have anything at all signed by Satoshi's PGP key? Peter Todd
2014-09-13 14:03 ` Jeff Garzik [this message]
2014-09-14 6:28 ` Peter Todd
2014-09-15 7:23 ` Thomas Zander
2014-09-15 9:49 ` Melvin Carvalho
2014-09-15 13:08 ` Jeff Garzik
2014-09-15 13:32 ` Brian Hoffman
2014-09-15 14:33 ` Jeff Garzik
2014-09-15 14:49 ` Brian Hoffman
2014-09-15 14:55 ` Pieter Wuille
2014-09-15 14:38 ` ThomasZander.se
2014-09-15 15:10 ` Thomas Zander
2014-09-15 15:51 ` Matt Whitlock
2014-09-15 16:07 ` Thomas Zander
2014-09-15 16:10 ` Gregory Maxwell
2014-09-15 16:20 ` Peter Todd
2014-09-15 14:44 ` Venzen
2014-09-15 18:06 ` 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=CAJHLa0MaE3Ki5Hs4Tu4dQNBW-EL-857N2kf-fVxYcXM6OO-84w@mail.gmail.com \
--to=jgarzik@bitpay.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pete@petertodd.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