From: "Joachim Strömbergson" <joachimstr@protonmail•com>
To: Gleb Naumenko <naumenko.gs@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Signaling support for addr relay (revision #1)
Date: Thu, 24 Oct 2019 08:01:49 +0000 [thread overview]
Message-ID: <1k3NxcpF9ShapWuKBA705zVwn1s0zgDOJywNrzIgBOetBsO75i8t9eO1TD0f9giGT74jJxtMjf25gj8T7Dj63CrooStdeT9-r2XLruXdHqo=@protonmail.com> (raw)
In-Reply-To: <485c6620-4927-4f44-b060-a3be1c31f135@Spark>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
> Anyway, according to the current considerations I explained in this email, I’d suggest extending BIP-155 with per-link-direction negotiation, but I’m interested in the opinion of the community.
I don't have a strong opinion here but intuitively, it seems to me that per-link variant makes better sense as I currently can't imagine the future requirement for completely opting out.
[-- Attachment #2: Type: text/html, Size: 603 bytes --]
prev parent reply other threads:[~2019-10-24 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fd174eb5-3699-4eed-b11e-e0370da63598@Spark>
2019-10-23 21:52 ` Gleb Naumenko
2019-10-24 8:01 ` Joachim Strömbergson [this message]
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='1k3NxcpF9ShapWuKBA705zVwn1s0zgDOJywNrzIgBOetBsO75i8t9eO1TD0f9giGT74jJxtMjf25gj8T7Dj63CrooStdeT9-r2XLruXdHqo=@protonmail.com' \
--to=joachimstr@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=naumenko.gs@gmail$(echo .)com \
/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