From: Mike Hearn <hearn@vinumeris.com>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XTs Tor IP blacklist downloading system has significant privacy leaks.
Date: Wed, 19 Aug 2015 17:45:06 +0200 [thread overview]
Message-ID: <CA+w+GKQEWB0ttJ_OykM46tnGCcm59-HqopoSA3Zh5d-b2iEuRw@mail.gmail.com> (raw)
In-Reply-To: <20150819022528.GA8920@muck>
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
The code was peer reviewed, in the XT project. I didn't bother submitting
other revisions to Core, obviously, as it was already rejected.
The quantity of incorrect statements in this thread is quite ridiculous.
[-- Attachment #2: Type: text/html, Size: 302 bytes --]
next prev parent reply other threads:[~2015-08-19 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 1:08 [bitcoin-dev] Bitcoin XTs Tor IP blacklist downloading system has significant privacy leaks Christophe Biocca
2015-08-19 1:36 ` Peter Todd
2015-08-19 1:48 ` Gregory Maxwell
2015-08-19 2:25 ` Peter Todd
2015-08-19 15:45 ` Mike Hearn [this message]
2015-08-19 18:51 ` Btc Drak
-- strict thread matches above, loose matches on Subject: below --
2015-08-18 23:31 F L
2015-08-18 23:56 ` Andrew LeCody
2015-08-19 0:00 ` Patrick Strateman
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=CA+w+GKQEWB0ttJ_OykM46tnGCcm59-HqopoSA3Zh5d-b2iEuRw@mail.gmail.com \
--to=hearn@vinumeris.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--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