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
>
>
>
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
