TCP hole punching for Bitcoin nodes behind home NATs?

The discourse raises critical considerations regarding the implementation and utility of a new networking feature, questioning its problem-solving capacity and overall desirability for most node operators. The primary concern revolves around whether the capability of accepting inbound connections is beneficial or poses potential risks, especially in terms of security. While the feature allows nodes to connect directly despite obstacles such as NAT or fluctuating IP addresses, which is advantageous for maintaining stable connections with known entities, it simultaneously opens up avenues for potential misuse by attackers. This duality suggests that while direct connectivity can be valuable, it likely requires stringent authentication measures, possibly making solutions like VPNs more suitable.

Furthermore, the conversation explores the concept of temporary, dynamic connections with various peers primarily for the purpose of data synchronization such as headers, blocks, and mempool information. This approach could enhance the network's performance and resilience without significantly increasing vulnerability, as it minimizes the duration and control an attacker might have over these connections. Suggesting an alternative method where nodes randomly connect and request introductions to other nodes could potentially distribute network load and optimize connectivity. However, this would necessitate a robust framework to manage these interactions securely and efficiently, ensuring that the network benefits outweigh the risks involved.