[BIP Draft] P2P UTXO Set Sharing

The discussion revolves around the implementation and security aspects of a Bitcoin feature, highlighting the reliance on SPV (Simplified Payment Verification) during certain operational phases. The main contention is that validating headers without verifying transaction inclusion is ineffective during the critical period before full node validation occurs. This approach, while it may appear to bolster security, actually aligns closely with the SPV model but introduces more complexity and higher startup costs.

The feature's primary function is described as allowing node use without full validation, which poses significant security risks, particularly in scenarios where transaction or block verifications are absent. This method assumes validity based solely on inclusion, following a strong chain which mimics the SPV security model but includes additional steps that potentially degrade its efficiency.

Furthermore, the feature incurs various disadvantages compared to traditional SPV, such as increased initial download requirements and greater wallet complexity due to the necessity of managing dual chain states. There are also issues with the availability of inclusion proofs for transactions presumed confirmed within a specific timeframe, thereby increasing the risk of denial-of-service attacks due to reliance on trust in the assumption phase. This could lead to unnecessary validations of the entire chain, costing time and resources without adding real security benefits.

In conclusion, the argument suggests that this feature compromises the trustless nature of peer-to-peer networks by integrating a semi-secure model that could extend indefinitely, making it an unsuitable long-term solution. The critique underscores the importance of reconsidering the implementation to prevent potential security flaws inherent in adopting an SPV-like model within the Bitcoin core network.