1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
|
Return-Path: <ctpacia@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9A34E71
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 24 Mar 2016 17:20:50 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com
[209.85.220.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2978417A
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 24 Mar 2016 17:20:50 +0000 (UTC)
Received: by mail-qk0-f174.google.com with SMTP id s68so22668099qkh.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 24 Mar 2016 10:20:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to; bh=U4jhdA3sbjIsVFU0kvhpSA0SfkDK6ye7hWsWbT6twCc=;
b=i5qmniVsmM5YBS4UBc7Yhym9GDklwSSLlZfV90WyBoDR4QgZmMyDdbgdmPKpmFBEzp
51dWi0qFvW40UitHgtEBrSlrfuqS+thh5kp0UD0/vHG84ogOLJW6Nf/GmbauKj5+JBva
8Lw1f4A1R3xkitqyhzwpgtG1MK7yio1l+7tlneZoYrZwY+q4cuEmHYR4l6NXi3nfSER6
c7Yv89dUDE9jwie/FoSAir2z7zjU8Cei/iwdKVBCmH58WyBkefd9cRtVtGeI+I4Qk3rU
D4jXBjAg/pmKZZ0nCLZwgyt9jUNh4g3gtjoY54vA1kk7tE9179NAHUVu8pa1rQ5B3S4E
v1FA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to;
bh=U4jhdA3sbjIsVFU0kvhpSA0SfkDK6ye7hWsWbT6twCc=;
b=BhVUPsjpUpTYRQRjJAE0PkLvU2bIja8mnrhn3x9vl6DwO9hxWaTZmBuFEw2J7GjwBF
UzBONlF0MxfvFDmYcMRTbK8YWiJlQKKTt9umWBUH1VBtcUKCBht7ALdRcoY3xrqmK8ZQ
tVIkdZJz+PFiPskiPAaNjNy55lfGlYIFO+c8kU4HFPxSMD84ldc8DBi71/tV7MzGFFAe
+DChHgTSzxPpFA3kF53qVC9qTtVcgPjmKhNuvqOenvf9cPHJI1UuTh/KXVanJHolUh6F
TtL1kJIWCMatsWJlT+YTXqldbOSB1tbItOf2xZFEg8UQ1wCGqp5NK43ur3Whk8MhY3EO
3ayQ==
X-Gm-Message-State: AD7BkJJ36FjZp+O7diXjraUXwwqe5+qa866+nPOkv0kZp7gIEMibykff5JptslRNTBaAXQ==
X-Received: by 10.55.72.196 with SMTP id v187mr11990037qka.97.1458840049313;
Thu, 24 Mar 2016 10:20:49 -0700 (PDT)
Received: from ?IPv6:2601:18d:8302:3e0:55fc:f806:e14e:b537?
([2601:18d:8302:3e0:55fc:f806:e14e:b537])
by smtp.gmail.com with ESMTPSA id
x124sm3611251qhc.42.2016.03.24.10.20.48
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLSv1/SSLv3 cipher=OTHER);
Thu, 24 Mar 2016 10:20:48 -0700 (PDT)
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"
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,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
X-Mailman-Approved-At: Thu, 24 Mar 2016 21:35:22 +0000
Subject: Re: [bitcoin-dev] p2p authentication and encryption BIPs
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: Thu, 24 Mar 2016 17:20:50 -0000
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--
|
