From: Tim Ruffing <crypto@timruffing•de>
To: bitcoin-dev@lists•linuxfoundation.org
Cc: Dhruv M <dhruv@bip324•com>
Subject: Re: [bitcoin-dev] Refreshed BIP324
Date: Wed, 11 Oct 2023 22:52:52 +0200 [thread overview]
Message-ID: <1c32b9c17a7a3ad6646994335c69155b65ac4f8f.camel@timruffing.de> (raw)
In-Reply-To: <56677685-619a-691f-d5bc-54b69fdb6ed2@bip324.com>
Hello,
We'd like to announce two recent updates to BIP324 ("Version 2 P2P
Encrypted Transport Protocol"). Some of these changes affect semantics
and some are backwards-incompatible.
While we are not aware of any implementations of BIP324 except the one
in Bitcoin Core (see https://github.com/bitcoin/bitcoin/issues/27634 ),
the purpose of the email is to inform anyone involved in other
implementation efforts. At this point, we don't expect any further
backwards-incompatible changes.
https://github.com/bitcoin/bips/pull/1496 did multiple small changes:
* Incoming v1 connections are now detected based on first 16 bytes
they sent (instead of 12), which improves accuracy. If the incoming
v1 connection appears to come from a wrong network (due to non-
matching "network magic" bytes), responders may now drop the
connection immediately.
* The BIP330 message types have been dropped from the short encodings
list in the BIP. It feels like it shouldn't be BIP324's goal to
predict future protocol improvements.
https://github.com/bitcoin/bips/pull/1498 introduced a backwards-
incompatible change:
* The garbage authentication packet is removed by merging it with the
version packet. This simplifies the protocol implementation by
consolidating the states and removing the special case of "ignoring
the ignore bit." The freedom to choose the contents of the garbage
authentication packet has also been removed, leading to easier
testing and implementation.
We also did some editorial improvements. The most recent revision of
the BIP324 can be found at:
https://github.com/bitcoin/bips/blob/master/bip-0324.mediawiki
Best,
Dhruv, Tim, and Pieter
On Sat, 2022-10-08 at 12:59 +0000, Dhruv M wrote:
> Hi all,
>
> We have refreshed the proposal for BIP324, a new bitcoin P2P protocol
> featuring opportunistic encryption, a mild bandwidth reduction, and
> the
> ability
> to negotiate upgrades before exchanging application messages. We'd
> like
> to invite community members to review the BIP[1] and the related
> Bitcoin
> Core
> code[2].
>
> The proposal has a rich history[3]. The big changes since the last
> public
> appearance[4] are:
>
> * Elligator-swift encoding for the pubkeys in the ECDH exchange to
> obtain a pseudorandom bytestream
> * x-only ECDH secret derivation
> * Transport versioning that allows for upgradability
> * Trafic shapability using decoy packets and a shapable handshake
> * Complete rewrite of the BIP text
>
> We look forward to your review and comments.
>
> -Dhruv, Tim and Pieter
>
>
> [1] BIP Pull Request: https://github.com/bitcoin/bips/pull/1378
>
> [2] All historical and current PRs:
> https://bip324.com/sections/code-review/
>
> [3] https://bip324.com/sections/bip-review/
>
> [4] https://gist.github.com/dhruv/5b1275751bc98f3b64bcafce7876b489
>
>
>
prev parent reply other threads:[~2023-10-11 20:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 12:59 Dhruv M
2022-10-26 16:39 ` Pieter Wuille
2022-10-27 7:28 ` Vasil Dimov
2022-11-03 17:53 ` Murch
2022-11-03 22:26 ` Jonas Schnelli
2022-11-08 3:20 ` Anthony Towns
2022-11-10 21:23 ` Pieter Wuille
2022-11-12 3:23 ` Pieter Wuille
2022-11-12 18:52 ` Yuval Kogman
2022-11-18 8:24 ` Anthony Towns
2023-01-05 22:06 ` Pieter Wuille
2023-01-05 23:12 ` Anthony Towns
2023-01-09 8:11 ` Anthony Towns
2023-02-16 17:43 ` Dhruv M
2023-02-17 15:51 ` Anthony Towns
2023-02-17 22:13 ` Pieter Wuille
2023-02-19 23:56 ` Anthony Towns
2023-02-20 15:22 ` Pieter Wuille
2023-02-21 16:03 ` Anthony Towns
2023-02-28 18:07 ` Dhruv M
2023-02-28 21:02 ` Erik Aronesty
2023-10-11 20:52 ` Tim Ruffing [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=1c32b9c17a7a3ad6646994335c69155b65ac4f8f.camel@timruffing.de \
--to=crypto@timruffing$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dhruv@bip324$(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