From: Matt Corallo <lf-lists@mattcorallo•com>
To: "Mr. Lee Chiffre" <lee.chiffre@secmail•pro>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] v3 onion services
Date: Sun, 17 Nov 2019 18:42:03 -0500 [thread overview]
Message-ID: <5E1011A2-9FDD-4FFF-B5AF-B35B7C375A5E@mattcorallo.com> (raw)
In-Reply-To: <8fd4e30c4c1c24442686dd51727e75cc.squirrel@giyzk7o6dcunb2ry.onion>
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
next prev parent reply other threads:[~2019-11-17 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 4:33 Mr. Lee Chiffre
2019-11-17 15:35 ` s7r
2019-11-17 20:04 ` LORD HIS EXCELLENCY JAMES HRMH
2019-11-17 23:01 ` Christopher Allen
2019-11-17 23:42 ` Matt Corallo [this message]
2019-11-18 11:59 ` Aymeric Vitte
2019-11-18 12:34 ` LORD HIS EXCELLENCY JAMES HRMH
[not found] ` <46FCD14B-02CC-4986-9C60-D8EC547F33FA@carldong.me>
2019-11-18 16:44 ` Carl Dong
2019-11-18 22:19 ` Aymeric Vitte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5E1011A2-9FDD-4FFF-B5AF-B35B7C375A5E@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lee.chiffre@secmail$(echo .)pro \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox