Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Matt Corallo <lf-lists@mattcorallo.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 17 Nov 2019 18:42:03 -0500
Message-Id: <5E1011A2-9FDD-4FFF-B5AF-B35B7C375A5E@mattcorallo.com>
References: <8fd4e30c4c1c24442686dd51727e75cc.squirrel@giyzk7o6dcunb2ry.onion>
In-Reply-To: <8fd4e30c4c1c24442686dd51727e75cc.squirrel@giyzk7o6dcunb2ry.onion>
To: "Mr. Lee Chiffre" <lee.chiffre@secmail.pro>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] v3 onion services
Precedence: list

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 =E2=80=9Caddrv2=E2=80=9D. Further review and contributions to tha=
t effort is, as always, welcome.

> On Nov 17, 2019, at 00:05, Mr. Lee Chiffre via bitcoin-dev <bitcoin-dev@li=
sts.linuxfoundation.org> wrote:
>=20
> =EF=BB=BFRight 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?
>=20
>=20
> --=20
> lee.chiffre@secmail.pro
> PGP 97F0C3AE985A191DA0556BCAA82529E2025BDE35
>=20
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev