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
|
Return-Path: <lee.chiffre@secmail.pro>
Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 2BC99C07AC
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 17 Nov 2019 04:41:51 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by hemlock.osuosl.org (Postfix) with ESMTP id 15C9B87E58
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 17 Nov 2019 04:41:51 +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 zc7ObxyeLMwS
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 17 Nov 2019 04:41:50 +0000 (UTC)
X-Greylist: delayed 00:08:16 by SQLgrey-1.7.6
Received: from secmail.pro (secmail.pro [146.185.132.44])
by hemlock.osuosl.org (Postfix) with ESMTP id 8198387E56
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 17 Nov 2019 04:41:50 +0000 (UTC)
Received: by secmail.pro (Postfix, from userid 33)
id 5BFABDF9FB; Sun, 17 Nov 2019 04:30:37 +0000 (UTC)
Received: from secmailw453j7piv.onion (localhost [IPv6:::1])
by secmail.pro (Postfix) with ESMTP id E5D45D3449
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 16 Nov 2019 20:33:31 -0800 (PST)
Received: from 127.0.0.1
(SquirrelMail authenticated user lee.chiffre@secmail.pro)
by giyzk7o6dcunb2ry.onion with HTTP; Sat, 16 Nov 2019 20:33:31 -0800
Message-ID: <8fd4e30c4c1c24442686dd51727e75cc.squirrel@giyzk7o6dcunb2ry.onion>
Date: Sat, 16 Nov 2019 20:33:31 -0800
From: "Mr. Lee Chiffre" <lee.chiffre@secmail.pro>
To: bitcoin-dev@lists.linuxfoundation.org
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Mailman-Approved-At: Sun, 17 Nov 2019 05:05:19 +0000
Subject: [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: Sun, 17 Nov 2019 04:41:51 -0000
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
|
