Waku v2 meshsub heartbeat limits in high-churn production environments

Waku v2 uses libp2p gossipsub with meshsub for message propagation across the peer-to-peer network. While local development often runs with default heartbeat intervals, production deployments face higher peer churn and variable network conditions that can destabilize the mesh.

The meshsub protocol relies on periodic heartbeat messages (IHAVE/IWANT) to maintain topic mesh connectivity. In high-churn environments, the default heartbeat interval may be too aggressive or too conservative, leading to either excessive bandwidth consumption or mesh partition and message loss. The configuration parameters heartbeatInterval and fanoutTTL directly control this behavior, but documented guidance for production tuning remains sparse.

• What are the practical bounds for heartbeatInterval when the node operates behind a load balancer with connection timeouts?
• How does fanoutTTL interact with libp2p connection manager limits under sustained churn?