public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Carl Dong <contact@carldong.me>
To: "Mr. Lee Chiffre" <lee.chiffre@secmail.pro>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] v3 onion services
Date: Mon, 18 Nov 2019 16:44:00 +0000	[thread overview]
Message-ID: <D16E0A83-67C2-4727-9FA0-410C43099CD0@carldong.me> (raw)
In-Reply-To: <46FCD14B-02CC-4986-9C60-D8EC547F33FA@carldong.me>

Hi Mr. Lee Chiffre,

I have been working on an implementation of addrv2 (BIP-155). Is this what you meant by I2P and Torv3 address support?

My WIP pull request: https://github.com/bitcoin/bitcoin/pull/16748
Merged BIP: https://github.com/bitcoin/bips/blob/master/bip-0155.mediawiki
Ongoing discussion: https://github.com/bitcoin/bips/pull/766
Note: Even though the pull request to the BIP repo is merged, we’re still discussing some details in the pull request thread and will amend the BIP once it seems like we’ve worked out all the kinks

Review and further discussion is very much welcome! :-)

Cheers,
Carl Dong
contact@carldong.me
"I fight for the users"

> On Nov 16, 2019, at 11:33 PM, 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




  parent reply	other threads:[~2019-11-18 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17  4:33 [bitcoin-dev] v3 onion services 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
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 [this message]
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=D16E0A83-67C2-4727-9FA0-410C43099CD0@carldong.me \
    --to=contact@carldong.me \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=lee.chiffre@secmail.pro \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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