From c1e1cfebbbc946f957e39345b9224a05704f701d Mon Sep 17 00:00:00 2001 From: Marcin Rataj Date: Fri, 28 Nov 2025 23:19:03 +0100 Subject: [PATCH] docs: link sweep blogpost in Provide.DHT.SweepEnabled add link to Shipyard's "Provide Sweep: Solving the DHT Provide Bottleneck" blogpost and remove stale TODO placeholder --- docs/config.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/config.md b/docs/config.md index 7e894626d..23386f7e6 100644 --- a/docs/config.md +++ b/docs/config.md @@ -1945,8 +1945,6 @@ map CIDs to your peer ID, enabling content discovery across the network. While designed to support multiple routing systems in the future, the current default configuration only supports [providing to the Amino DHT](#providedht). - - ### `Provide.Enabled` Controls whether Kubo provide and reprovide systems are enabled. @@ -2190,6 +2188,8 @@ to `false`. > > Sweep mode achieves similar effectiveness to the Accelerated DHT client but with steady resource consumption. +For background on the sweep provider design and motivations, see Shipyard's blogpost [Provide Sweep: Solving the DHT Provide Bottleneck](https://ipshipyard.com/blog/2025-dht-provide-sweep/). + You can compare the effectiveness of sweep mode vs legacy mode by monitoring the appropriate metrics (see [Monitoring Provide Operations](#monitoring-provide-operations) above). > [!NOTE]