From e0af335152a351cc2bb85453c3efe2eb79e19258 Mon Sep 17 00:00:00 2001 From: jerzybrzoska <51721153+jerzybrzoska@users.noreply.github.com> Date: Fri, 5 Feb 2021 10:52:45 +0100 Subject: [PATCH] ch08.asciidoc: Implementation status of BIP-150 and BIP-151 ( In fact, [BIP-151](https://github.com/bitcoin/bips) was withdrawn. --- ch08.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch08.asciidoc b/ch08.asciidoc index b5e4f7bd..bf3d7f39 100644 --- a/ch08.asciidoc +++ b/ch08.asciidoc @@ -313,7 +313,7 @@ You can find more instructions on running Bitcoin Core as a Tor hidden service i ((("Peer-to-Peer authentication and encryption")))((("bitcoin improvement proposals", "Peer Authentication (BIP-150)")))((("bitcoin improvement proposals", "Peer-to-Peer Communication Encryption (BIP-151)")))Two Bitcoin Improvement Proposals, BIP-150 and BIP-151, add support for P2P authentication and encryption in the bitcoin P2P network. These two BIPs define optional services that may be offered by compatible bitcoin nodes. BIP-151 enables negotiated encryption for all communications between two nodes that support BIP-151. BIP-150 offers optional peer authentication that allows nodes to authenticate each other's identity using ECDSA and private keys. BIP-150 requires that prior to authentication the two nodes have established encrypted communications as per BIP-151. -As of January 2017, BIP-150 and BIP-151 are not implemented in Bitcoin Core. However, the two proposals have been implemented by at least one alternative bitcoin client named bcoin. +As of February 2021, BIP-150 and BIP-151 are not implemented in Bitcoin Core. However, the two proposals have been implemented by at least one alternative bitcoin client named bcoin. BIP-150 and BIP-151 allow users to run SPV clients that connect to a trusted full node, using encryption and authentication to protect the privacy of the SPV client.