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
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
|
Return-Path: <vitteaymeric@gmail.com>
Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 7DBA6C07AC
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Nov 2019 11:59:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by hemlock.osuosl.org (Postfix) with ESMTP id 7475D87DB1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Nov 2019 11:59:04 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from hemlock.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id zpzai-+S+yAO
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Nov 2019 11:59:03 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-wm1-f68.google.com (mail-wm1-f68.google.com
[209.85.128.68])
by hemlock.osuosl.org (Postfix) with ESMTPS id F065587D76
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Nov 2019 11:59:02 +0000 (UTC)
Received: by mail-wm1-f68.google.com with SMTP id q70so17053110wme.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Nov 2019 03:59:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:references:from:openpgp:autocrypt:cc:message-id:date
:user-agent:mime-version:in-reply-to:content-language;
bh=qekr/0pbu/2passMKUubdpywDxJj5//bjNxhrw7/M9o=;
b=PX3JptBjBDsLo7c3gj9CCkS8OKi5dwxlW1TvXffxGV8tS6ZjqmeNn7iDTQGzrrn83u
fzEoOOyjULO0HIXbcX5Qm4AN8lqErQTAwr2IZl1+VXtcmgPf8uFn/D9HAVvwCk/oCTF9
PJJ1//ylwV/6B78Pj01TyCmuBRi8olKodH45DH2ykiVB1m5a3G3BXu9OFhmwne/R+xei
7fpE2izTkUOIt+9OuVodQiMjdUnnddJ2t64kfHKQ5lBDkVI0fBVMvS+63hzQ32u5wPAx
H/BL0YIVBCGIEVeYHN/6LY9PpOX/pG4GWMAdvwISrzgZzrvQfCgGjl7k0yzKWaRYF+VU
mBgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt:cc
:message-id:date:user-agent:mime-version:in-reply-to
:content-language;
bh=qekr/0pbu/2passMKUubdpywDxJj5//bjNxhrw7/M9o=;
b=ihFAGhx+QG/V9ZgkipusMoZtH0sLOTyPKkg3pyESWQAh9qBCeq8zbSgQzFM9EIhsZd
Hiz74BHQR5eMkK7y6uceNaRbBI3HL1y5IFsrnX4D3cOKNSj1XTUDpHX6lB3Z6JhLbUN5
5UUp0NxbupVEZr+moj+Sj3jmEqqn+9nTbkiivUiU0xO5a2THCMYR2GCBEhZHZY5HMC8D
VjGac3PCMVhVohUuPc7U5iS8mErBJLPCJmqWvcY7/YumjF5eJ8ea05/JHgBJ2sp+v2PU
DcGuNQlPidIZq9gnmkFR6SEACku5UpWWY71rQ3osW6+Ki+ATLLjg8IwwEL1tRN35gFxo
0kvQ==
X-Gm-Message-State: APjAAAWxCt1OMOKo+UQbS9mG93po+pNAnfrMYVlSFY69/WfSjFHZJT4d
vBuqi20CAlo5NfEMUeDe87M=
X-Google-Smtp-Source: APXvYqyATGjJYc9Ap5HTvotpzY7JNwaGgI4O25otY8JiHbWhJTBcgOLdlcVVU50ZfgB8IEpwb0bYnQ==
X-Received: by 2002:a05:600c:2102:: with SMTP id
u2mr26285636wml.49.1574078341224;
Mon, 18 Nov 2019 03:59:01 -0800 (PST)
Received: from ?IPv6:2a01:cb1d:44:6500:9d6d:71b2:cb71:cb17?
([2a01:cb1d:44:6500:9d6d:71b2:cb71:cb17])
by smtp.googlemail.com with ESMTPSA id n13sm19671086wmi.25.2019.11.18.03.59.00
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Mon, 18 Nov 2019 03:59:00 -0800 (PST)
To: Matt Corallo <lf-lists@mattcorallo.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
"Mr. Lee Chiffre" <lee.chiffre@secmail.pro>
References: <8fd4e30c4c1c24442686dd51727e75cc.squirrel@giyzk7o6dcunb2ry.onion>
<5E1011A2-9FDD-4FFF-B5AF-B35B7C375A5E@mattcorallo.com>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Openpgp: preference=signencrypt
Autocrypt: addr=vitteaymeric@gmail.com; prefer-encrypt=mutual; keydata=
mQINBFdW8uABEAC7HJScbB2d/lmYoY5Cn9loEjJwfLs1LC3om030bWFGiH3Ceo5XeHUT94rw
Pi+HaHU8ea94425SXIFsnqp/ouoT/8Ffn6vED0OoRmK0jE4fqDApXSpoL2mHX9PAGdUItMtD
YrxBiBZNfMkctEsm4NrQ4TCvB3Yrm6Fc69inXJjUoYgPw5tHafEeI8Qwh0j99JZZDKcAqIra
JF3MPc59rATz0qOJtRP9EpsPVFwjJe13zN6CHILwiVgrL8EtT5WKCVO6ATxh60LHi8+MwPxV
V31zp/NNI5Hck+XocEMO98ZvUu9X8ZxmnOk/+9pBxXEwUqSGUNWdmPJLncpI23Usce3u/MOo
M2C4T4rD4J0XrXiyBvbeTvwq4qVNlyggeWzlBH+YpEYgDctPq4gNh4eoTtAkf8URtBeke5bQ
CGdaZt/jxv8nvmxs9V/iSyg5ldJLQktHStXOo0OZ7FEB2C6Ggtymm4hm2MHYg07Q1MGJrFLa
oJZkJ3JeXnVsZMam7ypQtld6rRa96CvH+llXwux6aQ5hKdzmBBMQ10LlkZhkExgTawbeqdiG
RMP2DjD5go6TPdAHS4NN34SBkrTWLqgWOjN/lnG77bbLnpMl0P+xBTuqw1oSXaDbcdHE2nGY
lRno/ZZIfr+1Bq56DZLBX/WpnAT4f5WtofL4CxQM9SbG6byyewARAQABtCJBeW1lcmljIFZp
dHRlIDxheW1lcmljQHBlZXJzbS5jb20+iQI/BBMBCAApBQJXVvLgAhsjBQkJZgGABwsJCAcD
AgEGFQgCCQoLBBYCAwECHgECF4AACgkQKh17NCYnrDm3WhAAlYmgtSmtfqjBvQMqkmtqiQJA
aZkzFZWt6+zroduHH5/Tp8jh73gFqCUyRrl/kcKvs2+XQhfrOwk1R6OScF25bpnrZSeuyJnZ
MZu4T0P2tGS8YdddQvWUHMtI9ZnQRuYmuZT23/hgj1JnukuGvGLeY0yDUa1xFffPN39shp5X
FPMcpIVOV3bs+xjAdsyfRyO3qJAD1FGiR7ggJeoaxUbKZ6NtcVUPPRMjVTKfopkuDwKY318m
BE0epfxSZ/iRhsJ0/sREUWgbgq4/QvCFwBKzgz7fTikGmf8OELWSdofmXs7gOtmMc3el8fJu
W8PVa/OsIQHDmwSzvxmE8ba5M8bdwOYEraTWFArIymAAtRXKxmuYpkqKfeSlbCwae3W+pgNT
8nKYRVAFlMtIxYkmPYyMTk9kCscmSqugGWbWdnqe/dhVaa31xa1qO1tDH24D2/tjCJRQt4Jk
AEWNSmjCmjfeArMEFTGlZwMTAjVXErLSPbLOsZiZhD9sjvSbfzrtJiMli2h9+Dvds+AJk1PM
O8LW7cCNyFoCk4OdAxzJHobZ25G+uy4NSQEHgxLC2iuh/tugz1tOHnQczPc/3AkVVI9A5DF1
gbVRBJh6rI7sAcwuR76uoOs0Rpp7r6I66xqU/5eq8g1OsJp89tw0ppSIa0YmaxNqQZ0l3rVX
o/ZwpBjtNQS5Ag0EV1by4AEQANhlz3Ywff4dY1HTdn05v0wVUxZzW2PUih+96m6EhpUrD9BT
vxriKtbgxm/zl+5YAlThbrk9f0QyVTHJ95Z1/M5qjuksP9Zn3qZ/8ylANDkN2s3z8Bq/LJA+
u7+APhMqyFWK0FqNCOogClvijiKPEzkU6tmDGO6wZ5pR/u8Fdq7DGQgwgyGZZc7qstte0M7l
yx7bVRlPBqvd6kyX3YubQHzkctf46nFjiYZgKawdWFsA3PCdSBupbhixL5d/t1UK9ZTiQJcf
0uhHzT06qwolFrm/ugkLDHtE4Zo3BuKch47Sms8P2hJ08gABxeJHg0ZgkIUy/Xf4nHbDCBJw
T8tE8pWYWA2ECiPNo0TOCMVOueEzISUNKINfCuFHSbMQU39hgt3ofxODbAjOiO3e/iu1ptck
AkuVBdtjOBP4tHRGxVrbf5EuAV5U5xtiSxMwMgojg0GIXZjnT/8uvWqcLqtJILRMmmu+WNvD
oxuiJzcTJhDai9oujmxQwcpMvgrBB89KSTDyitO5XVjZqaR7Zxvvn3rM4bAms/lotv9+pTyh
spazTIxb80u0ifJ6y1RxAkxQCfWwps1i3VbsM6OKX78aUyOf5V4ihXF57M37tOqPRwFvz6a+
AIIhUNMTLo2H+o6Vw9qbX8SUxPHPs6YpJ8lWQJ9OMWHE+SbaDFAi/D5hYRubABEBAAGJAiUE
GAEIAA8FAldW8uACGwwFCQlmAYAACgkQKh17NCYnrDmk4Q/9Fuu0h5HvIiO3ieYA2StdE7hO
vv2THuesjJDsj6aQUTgknaxKptJogNe3dDyIT+FHxXmCw0Nrbm9Q3ryl80z/G9utfFNO3Gwc
q31QW3n3LJHnpqdrV3WsRzT5NwJMVtiIAGRrX8ZomtarWHT0PeEHC2xBdFzRrJtmkrwer0Wc
0nBzD7vk1XEXC9nODbmlgsesoHFgRwQBst3wClCbX1gv8aSfxQNpaf9UBC8DmyrQ621UXpBo
PvcFEtWxV44vJfP0WOLCCN0Pzv2F2I66iKo7VMqbr5jlNAXJN9I1hXb7qwYJmBC9j5oeEoqv
A9d44WWpxrdAr8qih4Nv89k9+9F6NoqORY3FGuVDKiW8CVhCmGT7bIvNeyicVBZFipXqPcKL
VFduO2c5Ubc2npMWLUF1k9JJc9tH75l3+F/0RbYVTzGAZ+zSaudwR6h8YiCN2DBZGZkJEZbh
3X/l6jtijMN/W9sPHyyKvm/TmeEC27S3TqZPZ8PUQLxZC70V6gMbenh01JdSQsn5t8Ru0RNh
Blt0g7IyZyIKCE9b+TyzbYpX6qgqEBUHia5b0vyPtQacWQlZ8uqnghAqNkLluEsy7Q/7xG6M
wXUYEDsFOmB9dKOzcAOIhpxlVjSKu5mzXJ11sEtE8nyF5NJ/riCA7FGcjlki3zIpzQUNo9v7
vXl2h6Tivlk=
Message-ID: <b498c783-f8ec-3078-a0f9-c8a1dd2f830f@gmail.com>
Date: Mon, 18 Nov 2019 12:59:03 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:60.0) Gecko/20100101
Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <5E1011A2-9FDD-4FFF-B5AF-B35B7C375A5E@mattcorallo.com>
Content-Type: multipart/alternative;
boundary="------------A8272E27164A6484DE3A1333"
Content-Language: fr
Cc: fontainedenton@googlemail.com
Subject: Re: [bitcoin-dev] v3 onion services
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol 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: Mon, 18 Nov 2019 11:59:04 -0000
This is a multi-part message in MIME format.
--------------A8272E27164A6484DE3A1333
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
As I briefly sketched here before I think that a better long term
solution would be to link the bitcoin traffic with something like
node-Tor (https://github.com/Ayms/node-Tor)
Much more light (the whole code not minified is only ~1MB), not using
tons of libraries prone to security/maintenance issues, easy to
use/configure/maintain and you don't need the (heavy/complicate) onions
RDV concepts and addresses, which in addition is useless for bitcoin
As simple as a duplex stream *bitcoin.pipe(node-Tor)* inside servers or
browsers (difficult to imagine full nodes and the blocks inside browsers
but why not one day, so for light clients probably implementing part of
the bitcoin protocol like https://peersm.com/wallet, for now it's a
standalone offline webapp but of course it would be interesting to
connect it in a secure way to bitcoin nodes to retrieve info from the
utxo set and send txs for example since it's not obvious for users to
create their txs in its current form)
This would be a separate network using the Tor protocol over TCP,
WebSockets and WebRTC, making it possible also for browsers to relay the
traffic, probably the nodes discovery (to get the keys) could be linked
to the bitcoin peer discovery system (we just have to add the onion key
to the peer profile, and maybe long term id key), anyway that's simple
to setup, and probably for a p2p network 2 hops will be enough
I really don't think that the Tor network is designed and adapted to
support bitcoin nodes, using it for something else than browsing is just
a workaround and I would be surprised that the Tor project team
contradicts this and/or encourage this use
Le 18/11/2019 à 00:42, Matt Corallo via bitcoin-dev a écrit :
> There is effort ongoing to upgrade the Bitcoin P2P protocol to support other address types, including onion v3. There are various posts on this ML under the title “addrv2”. Further review and contributions to that effort is, as always, welcome.
>
>> On Nov 17, 2019, at 00:05, Mr. Lee Chiffre via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>> Right now bitcoin client core supports use of tor hidden service. It
>> supports v2 hidden service. I am in progress of creating a new bitcoin
>> node which will use v3 hidden service instead of v2. I am looking at
>> bitcoin core and btcd to use. Do any of these or current node software
>> support the v3 onion addresses for the node address? What about I2P
>> addresses? If not what will it take to get it to support the longer
>> addresses that is used by i2p and tor v3?
>>
>>
>> --
>> lee.chiffre@secmail.pro
>> PGP 97F0C3AE985A191DA0556BCAA82529E2025BDE35
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--------------A8272E27164A6484DE3A1333
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>As I briefly sketched here before I think that a better long term
solution would be to link the bitcoin traffic with something like
node-Tor (<a class="moz-txt-link-freetext" href="https://github.com/Ayms/node-Tor">https://github.com/Ayms/node-Tor</a>)</p>
<p>Much more light (the whole code not minified is only ~1MB), not
using tons of libraries prone to security/maintenance issues, easy
to use/configure/maintain and you don't need the
(heavy/complicate) onions RDV concepts and addresses, which in
addition is useless for bitcoin<br>
</p>
<p>As simple as a duplex stream <b>bitcoin.pipe(node-Tor)</b>
inside servers or browsers (difficult to imagine full nodes and
the blocks inside browsers but why not one day, so for light
clients probably implementing part of the bitcoin protocol like
<a class="moz-txt-link-freetext" href="https://peersm.com/wallet">https://peersm.com/wallet</a>, for now it's a standalone offline
webapp but of course it would be interesting to connect it in a
secure way to bitcoin nodes to retrieve info from the utxo set and
send txs for example since it's not obvious for users to create
their txs in its current form)<br>
</p>
<p>This would be a separate network using the Tor protocol over TCP,
WebSockets and WebRTC, making it possible also for browsers to
relay the traffic, probably the nodes discovery (to get the keys)
could be linked to the bitcoin peer discovery system (we just have
to add the onion key to the peer profile, and maybe long term id
key), anyway that's simple to setup, and probably for a p2p
network 2 hops will be enough</p>
<p>I really don't think that the Tor network is designed and adapted
to support bitcoin nodes, using it for something else than
browsing is just a workaround and I would be surprised that the
Tor project team contradicts this and/or encourage this use<br>
</p>
<div class="moz-cite-prefix">Le 18/11/2019 à 00:42, Matt Corallo via
bitcoin-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:5E1011A2-9FDD-4FFF-B5AF-B35B7C375A5E@mattcorallo.com">
<pre class="moz-quote-pre" wrap="">There is effort ongoing to upgrade the Bitcoin P2P protocol to support other address types, including onion v3. There are various posts on this ML under the title “addrv2”. Further review and contributions to that effort is, as always, welcome.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On Nov 17, 2019, at 00:05, Mr. Lee Chiffre via bitcoin-dev <a class="moz-txt-link-rfc2396E" href="mailto:bitcoin-dev@lists.linuxfoundation.org"><bitcoin-dev@lists.linuxfoundation.org></a> wrote:
Right now bitcoin client core supports use of tor hidden service. It
supports v2 hidden service. I am in progress of creating a new bitcoin
node which will use v3 hidden service instead of v2. I am looking at
bitcoin core and btcd to use. Do any of these or current node software
support the v3 onion addresses for the node address? What about I2P
addresses? If not what will it take to get it to support the longer
addresses that is used by i2p and tor v3?
--
<a class="moz-txt-link-abbreviated" href="mailto:lee.chiffre@secmail.pro">lee.chiffre@secmail.pro</a>
PGP 97F0C3AE985A191DA0556BCAA82529E2025BDE35
_______________________________________________
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>
<pre class="moz-quote-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>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>
--------------A8272E27164A6484DE3A1333--
|
