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
Marcin Rataj committed
Nov 28, 2025 at 23:19 UTC
c1e1cfebbbc946f957e39345b9224a05704f701d
1 file changed
+2
-2
docs/config.md
+2
-2
@@ -1945,8 +1945,6 @@ map CIDs to your peer ID, enabling content discovery across the network.
1945
While designed to support multiple routing systems in the future, the current
1946
default configuration only supports [providing to the Amino DHT](#providedht).
1947
1948
-<!-- TODO: See the [Reprovide Sweep blog post](https://github.com/ipshipyard/ipshipyard.com/pull/8) for detailed performance comparisons. -->
1949
-
1948
### `Provide.Enabled`
1949
1950
Controls whether Kubo provide and reprovide systems are enabled.
@@ -2190,6 +2188,8 @@ to `false`.
2188
>
2189
> Sweep mode achieves similar effectiveness to the Accelerated DHT client but with steady resource consumption.
2190
2191
+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/).
2192
+
2193
You can compare the effectiveness of sweep mode vs legacy mode by monitoring the appropriate metrics (see [Monitoring Provide Operations](#monitoring-provide-operations) above).
2194
2195
> [!NOTE]