From 5ace906873fc5d1757a86b016b5e731ab5decf1a Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 5 Nov 2026 00:10:24 +0100 Subject: stale delta offers --- docs/peers.md | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/peers.md') diff --git a/docs/peers.md b/docs/peers.md index 4775e85..fc4b6f1 100644 --- a/docs/peers.md +++ b/docs/peers.md @@ -172,6 +172,9 @@ other neighbours offer them too, and they would come once per offer. Offers that meanwhile wait; once the delta is in, the node syncs with those that offered, which then send only what is still missing. What a delta brought counts as known to its sender, as what its sync messages bring does: none of it goes back, by message or as a delta. +An offer made before its sender heard what the node has now (one that came behind the +chunks of the delta before it, say) would bring part of that again: such an offer isn't +fetched; the node's next message tells the sender, which offers afresh if still needed. Towards a peer on a slow link the limit is lower: a message is offered as a delta if it would take more than 5 s at the throughput measured to that peer (`syncThroughput`, -- cgit v1.3.1