# Quick peer gossip catchup protocol

**URL:** <https://delvingbitcoin.org/t/quick-peer-gossip-catchup-protocol/251>\
**Category:** Protocol Design\
**Tags:** lightning\
**Created:** [December 5, 2023, 3:22am UTC](https://delvingbitcoin.org/t/quick-peer-gossip-catchup-protocol/251 "2023-12-05T03:22:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![MattCorallo](https://delvingbitcoin.org/letter_avatar_proxy/v4/letter/m/e47c2d/32.png) [@MattCorallo](https://delvingbitcoin.org/u/MattCorallo)\
**Post date:** [December 5, 2023, 5:49am UTC](https://delvingbitcoin.org/t/quick-peer-gossip-catchup-protocol/251/2 "2023-12-05T05:49:50Z")

</div>

Can we accomplish this without any per-peer storage? Probably something like “the last time I was online, running, and received gossip was block header/timestamp X”. From there any peer that does receive-time tracking should be able to go back into their gossip history and check for everything newer than said time (minus a fudge factor).

Of course that assumes nodes keep track of when they received all gossip messages. Currently we only track that for channel announcements, not updates. TBH I’d really rather we Just Do Minisketch and move on rather than trying to keep applying bandaids to the current gossip.

---

_[View the full topic](https://delvingbitcoin.org/t/quick-peer-gossip-catchup-protocol/251)._