Return-Path: <hearn@vinumeris.com> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AA7F845E for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 22 Jul 2015 21:18:52 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 361D31AD for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 22 Jul 2015 21:18:52 +0000 (UTC) Received: by iebmu5 with SMTP id mu5so177062278ieb.1 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 22 Jul 2015 14:18:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vinumeris.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iqnKa/MG1LvJ33OCjgBKf2h2pC1k5cDXQfuDHn32ui0=; b=NHchNQRSlwhP2ZKeRAblh2I3nVj/lFF0Gbkyjbk1eoSB/e+eB5iH6CCTfYPyrgJrSY fE5L9XmG4ASYBat1Qdy4lp5TycNBKS+3FuR2rhIVvZhFbM78LpkaLSNgbjQbPPO0YjY8 Won3IGo7jzX3kWkB6JN+WkkMAwy8AlmF4bmPg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=iqnKa/MG1LvJ33OCjgBKf2h2pC1k5cDXQfuDHn32ui0=; b=J20Qyfr1oSlUYENJsCyMSCp4tk5JE659fkfk7+IyOL8QS2K9fstHsj4W6kGPrnerDb ofvX4Q1/TzHfEo54MDDRo+ovGfcOc+mVW31iAcIXKSB+TrVHC0uMr4oWefR1KdX5GEmX 0xupWSIjIl3if5CatrYIXz+wv0xAwQ/3sNua/zqOboK3kavfabqXj+zbs8o5bRrcSEw4 Tj6RKN49T5YYc6/5XapfvhEiNyMQmIr+yU0XR+LarpVgtiqo4yJn+5sZLydL9LW66Ae4 nZAe/Pa9QNAW0BoYm4n2cX7wHqmfI7/aQNfUumdg6pAvnFCCrDuUuF7iw/KExV7koh1f kQ8g== X-Gm-Message-State: ALoCoQnh3/b0zvbIhi5kjZtsFKdnrpxamrYhYmsF3yx3WthgELecAVeZeccE3PGBeOiimDjhUvKD MIME-Version: 1.0 X-Received: by 10.50.50.228 with SMTP id f4mr5784793igo.19.1437599931687; Wed, 22 Jul 2015 14:18:51 -0700 (PDT) Received: by 10.50.108.111 with HTTP; Wed, 22 Jul 2015 14:18:51 -0700 (PDT) In-Reply-To: <CA+ASnrG_sNRio03pr_F6vSepucG66=R+n_x7xREYqKPXOo9hyw@mail.gmail.com> References: <55AFBBE6.3060702@electrum.org> <CA+ASnrG_sNRio03pr_F6vSepucG66=R+n_x7xREYqKPXOo9hyw@mail.gmail.com> Date: Wed, 22 Jul 2015 23:18:51 +0200 Message-ID: <CA+w+GKSBN6P7k1iGWONc2D9d+CQL4PWcDZ6EkqW9mkZUDNAVcw@mail.gmail.com> From: Mike Hearn <hearn@vinumeris.com> To: =?UTF-8?B?Sm9zZXBoIEdsZWFzb24g4pGI?= <fireduck@gmail.com> Content-Type: multipart/alternative; boundary=047d7bd75cb041f62f051b7d510c X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] Making Electrum more anonymous X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Wed, 22 Jul 2015 21:18:52 -0000 --047d7bd75cb041f62f051b7d510c Content-Type: text/plain; charset=UTF-8 > > One solution would be for the client to combine all the addresses they are > interested in into a single bloom filter and send that to the server. > <snip extra ideas> Hey Joseph, All those ideas are ones we had years ago and they are implemented in the current Bitcoin protocol. The trick, as you may know, is this bit: The client would also need to be fairly clever > It turns out making a sufficiently clever client to fool even advanced observers is a lot of programming work, assuming you wish for the Ultimate Solution which lets you allocate a desired quantity of bandwidth and then use it to maximize privacy. --047d7bd75cb041f62f051b7d510c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= cc solid;padding-left:1ex"><div dir=3D"ltr"><div>One solution would be for = the client to combine all the addresses they are interested in into a singl= e bloom filter and send that to the server.</div></div></blockquote><div><b= r></div><div><snip extra ideas></div><div><br></div><div>Hey Joseph,<= /div><div><br></div><div>All those ideas are ones we had years ago and they= are implemented in the current Bitcoin protocol.</div><div><br></div><div>= The trick, as you may know, is this bit:=C2=A0</div><div><br></div><blockqu= ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s= olid;padding-left:1ex"><div dir=3D"ltr"><div>The client would also need to = be fairly clever</div></div></blockquote><div><br></div><div>It turns out m= aking a sufficiently clever client to fool even advanced observers is a lot= of programming work, assuming you wish for the Ultimate Solution which let= s you allocate a desired quantity of bandwidth and then use it to maximize = privacy.</div></div></div></div> --047d7bd75cb041f62f051b7d510c--