UX Issue: Jarring connection retry cycles during initial peer sync

[bayfitt]

Problem Description

During initial startup, Thunder shows multiple rapid connection/disconnection cycles with peers before achieving stable sync. This creates a jarring user experience where users might think the connection is failing and close the application.

Logs

2025-08-31T14:47:27.059377Z  INFO thunder::net:205: remove active peer: disconnected addr=172.105.148.135:4009
2025-08-31T14:47:27.060609Z  WARN thunder::node::net_task:1013: Connection to peer closed addr=172.105.148.135:4009
2025-08-31T14:47:37.098998Z  INFO thunder::net::peer:163: connected successfully to peer addr=172.105.148.135:4009
2025-08-31T14:47:42.118918Z  INFO thunder::net:205: remove active peer: disconnected addr=172.105.148.135:4009
2025-08-31T14:47:42.119149Z  WARN thunder::node::net_task:1013: Connection to peer closed addr=172.105.148.135:4009
2025-08-31T14:47:52.178567Z  INFO thunder::net::peer:163: connected successfully to peer addr=172.105.148.135:4009
2025-08-31T14:47:57.198576Z  INFO thunder::net:205: remove active peer: disconnected addr=172.105.148.135:4009
2025-08-31T14:47:57.198620Z  WARN thunder::node::net_task:1013: Connection to peer closed addr=172.105.148.135:4009
2025-08-31T14:48:07.241330Z  INFO thunder::net::peer:163: connected successfully to peer addr=172.105.148.135:4009
2025-08-31T14:48:12.264506Z  INFO thunder::net:205: remove active peer: disconnected addr=172.105.148.135:4009
2025-08-31T14:48:12.264779Z  WARN thunder::node::net_task:1013: Connection to peer closed addr=172.105.148.135:4009
2025-08-31T14:48:22.346108Z  INFO thunder::net::peer:163: connected successfully to peer addr=172.105.148.135:4009

Timeline

• ~6 connection/disconnection cycles over 45 seconds
• Each connection lasted only 5 seconds before disconnecting
• Eventually achieved stable connection and began syncing normally

Impact

• User Experience: Users may think connection is failing and close the application
• Trust: Repeated disconnect warnings create impression of instability
• Functionality: System works correctly after retry cycles, but UX is poor

Expected Behavior

• Either silent retries in background without logging disconnects as warnings
• Or clear user messaging like "Establishing peer connections..." during retry phase
• Avoid rapid connect/disconnect cycles that appear as connection failures

Environment

• Thunder Rust wallet connecting to mainchain
• Peer: 172.105.148.135:4009
• Application eventually syncs successfully after connection stabilizes

Priority

UX improvement - functionality works but user experience could be misleading