Optimize Stream Sync Peer Discovery: Reduce Startup Time to Seconds

[GheisMohammadi]

Summary

This PR addresses the critical issue where stream sync takes ~15 minutes to find enough peers on node startup, while restarting the service allows much faster peer discovery. The solution implements a comprehensive peer discovery optimization strategy with startup mode, network-aware limits, and improved timing algorithms.

Problem Statement

Issue: Stream sync on node startup takes approximately 15 minutes to find minimum streams and begin syncing, while restarting the service enables much faster peer discovery.

Root Causes:

• 30-second discovery intervals combined with cooldowns create long delays
• Hardcoded peer discovery limits not optimized for different networks
• No early exit mechanism when sufficient peers are found
• Inefficient timing algorithms with aggressive backoff

Solution Overview

1. Startup Mode Implementation

• Faster Initial Discovery: Reduced timeouts and intervals during first 10 minutes
• Early Exit: Automatically exits startup mode when enough streams are found
• Adaptive Timing: Different timing strategies for startup vs normal operation

2. Network-Aware Peer Discovery

• Configuration-Aligned: Target valid peers match actual stream sync requirements
• Network-Specific Limits: Different DHT request limits per network type
• Realistic Expectations: Success rates based on actual DHT behavior

3. Improved Timing Algorithms

• Centralized Constants: All timing values moved to const.go
• Adaptive Sleep: Increase sleep when peers found, decrease when none found
• Better Backoff: 30% decrease instead of aggressive /= 2

Configuration Alignment

Network	InitStreams	Target Valid	DHT Request	Success Rate
Mainnet	8	8	20	40%
Testnet	3	3	10	30%
Pangaea	3	3	10	30%
Partner	3	3	10	30%
Stressnet	4	4	12	33%
Devnet	4	4	12	33%
Localnet	4	4	12	33%