From 83e7eb8c08f008806459a0620d58a1e52a530d4b Mon Sep 17 00:00:00 2001 From: ziggie Date: Mon, 3 Aug 2026 19:18:05 -0300 Subject: [PATCH] docs: move gossip bounds note to v0.21.2 --- docs/release-notes/release-notes-0.21.2.md | 11 +++++++++++ docs/release-notes/release-notes-0.22.0.md | 11 ----------- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/release-notes/release-notes-0.21.2.md b/docs/release-notes/release-notes-0.21.2.md index cc96ab69b..82c8d420e 100644 --- a/docs/release-notes/release-notes-0.21.2.md +++ b/docs/release-notes/release-notes-0.21.2.md @@ -43,6 +43,16 @@ v0.20-era mandatory version so the v0.21 waiting proof migration runs without replaying older migrations against an already-initialized database. +* [Bounded the memory used while syncing the channel + graph](https://github.com/lightningnetwork/lnd/pull/10992). A peer replying + to our `query_channel_range` could previously make us buffer an + unpredictable number of short channel IDs, as the only limit was a coarse + 67MB cap on the bytes a single zlib-compressed reply could decompress to. + Replies are now capped at a precise number of short channel IDs, both + per-message and in aggregate across a single query, and the accumulated + reply state is released as soon as any reply fails validation so that a + peer cannot pin it by deliberately forcing an error. + # New Features ## Functional Enhancements @@ -107,3 +117,4 @@ * bitromortac * Jared Tobin +* Olaoluwa Osuntokun diff --git a/docs/release-notes/release-notes-0.22.0.md b/docs/release-notes/release-notes-0.22.0.md index 911782f3b..750a20069 100644 --- a/docs/release-notes/release-notes-0.22.0.md +++ b/docs/release-notes/release-notes-0.22.0.md @@ -55,16 +55,6 @@ the reported network statistics such as total network capacity, channel count and max out degree. -* [Bounded the memory used while syncing the channel - graph](https://github.com/lightningnetwork/lnd/pull/10992). A peer replying - to our `query_channel_range` could previously make us buffer an - unpredictable number of short channel IDs, as the only limit was a coarse - 67MB cap on the bytes a single zlib-compressed reply could decompress to. - Replies are now capped at a precise number of short channel IDs, both - per-message and in aggregate across a single query, and the accumulated - reply state is released as soon as any reply fails validation so that a - peer cannot pin it by deliberately forcing an error. - # New Features ## Functional Enhancements @@ -169,4 +159,3 @@ * Boris Nagaev * Erick Cestari * Jared Tobin -* Olaoluwa Osuntokun