From 8fd14bc45862155d6c011c215a596d62e0808437 Mon Sep 17 00:00:00 2001 From: Olaoluwa Osuntokun Date: Wed, 25 Aug 2021 16:46:34 -0700 Subject: [PATCH] docs/release-notes: add notes for new ping header in 0.14 --- docs/release-notes/release-notes-0.14.0.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/release-notes/release-notes-0.14.0.md b/docs/release-notes/release-notes-0.14.0.md index 94a8df3a3..d0d7dcff2 100644 --- a/docs/release-notes/release-notes-0.14.0.md +++ b/docs/release-notes/release-notes-0.14.0.md @@ -7,6 +7,25 @@ is only used for onion address connections, and clearnet for everything else. This new behavior can be added using the `tor.skip-proxy-for-clearnet-targets` flag. +## LN Peer-to-Peer Netowrk + +### Bitcoin Blockheaders in Ping Messages + +[In this release, we implement a long discussed mechanism to use the Lightning +Network as a redundant block header +source](https://github.com/lightningnetwork/lnd/pull/5621). By sending our +latest block header with each ping message, we give peers another source +(outside of the Bitcoin P2P network) they can use to spot check their chain +state. Peers can also use this information to detect if they've been eclipsed +from the traditional Bitcoin P2P network itself. + +As is, we only send this data in Ping messages (which are periodically sent), +in the future we could also move to send them as the partial payload for our +pong messages, and also randomize the payload size requested as well. + +The `ListPeers` RPC call will now also include a hex encoded version of the +last ping message the peer has sent to us. + ## Backend Enhancements & Optimizations ### Full remote database support