To: bitcoin-dev@lists.linuxfoundation.org
References: <56F2B51C.8000105@jonasschnelli.ch>
From: Chris <ctpacia@gmail.com>
Message-ID: <56F421F0.8090307@gmail.com>
Date: Thu, 24 Mar 2016 13:20:48 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56F2B51C.8000105@jonasschnelli.ch>
Content-Type: multipart/alternative;
	boundary="------------020105060903020703070701"
Subject: Re: [bitcoin-dev] p2p authentication and encryption BIPs
Precedence: list

This is a multi-part message in MIME format.
--------------020105060903020703070701
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Thanks for doing some work on this Jonas. It's something I've been
interested in for a while. I haven't had an opportunity to read the bips
but I will do so soon and comment.

As far as the use cases others mentioned, connecting and SPV wallet to
your full node is certainly one. It would make it easy to, say, connect
the android bitcoin-wallet to your own node. I've hacked on that wallet
to make it connect to my .onion node, but it's very slow border-line
unusable. Basic encryption and authentication would make that viable.

Also, while bloom filtering in bitcoinj is broken, it could be fixed by
just creating a single filter and filling it with 1000 addresses and
persisting it to disk. The main issue is you can't restore from seed
that way and would have to revert to what bitcoinj does now and blow
your privacy. If you had the ability to make an encrypted connection to
a trusted node just for restoring from seed, you could save your privacy
during a restore.

On 03/23/2016 11:24 AM, Jonas Schnelli via bitcoin-dev wrote:
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


--------------020105060903020703070701
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Thanks for doing some work on this Jonas. It's something I've been
    interested in for a while. I haven't had an opportunity to read the
    bips but I will do so soon and comment. <br>
    <br>
    As far as the use cases others mentioned, connecting and SPV wallet
    to your full node is certainly one. It would make it easy to, say,
    connect the android bitcoin-wallet to your own node. I've hacked on
    that wallet to make it connect to my .onion node, but it's very slow
    border-line unusable. Basic encryption and authentication would make
    that viable. <br>
    <br>
    Also, while bloom filtering in bitcoinj is broken, it could be fixed
    by just creating a single filter and filling it with 1000 addresses
    and persisting it to disk. The main issue is you can't restore from
    seed that way and would have to revert to what bitcoinj does now and
    blow your privacy. If you had the ability to make an encrypted
    connection to a trusted node just for restoring from seed, you could
    save your privacy during a restore. <br>
    <br>
    <div class="moz-cite-prefix">On 03/23/2016 11:24 AM, Jonas Schnelli
      via bitcoin-dev wrote:<br>
    </div>
    <blockquote cite="mid:56F2B51C.8000105@jonasschnelli.ch" type="cite"><br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------020105060903020703070701--