[BIP Draft] P2P UTXO Set Sharing

In a recent discussion regarding the Bitcoin Core pull request titled "p2p: UTXO set sharing" (#35054), there has been a proposal that suggests omitting full validation of the UTXO set by nodes, presenting this initially as a thought experiment. This idea has sparked significant debate due to its potential implications on the security model of Bitcoin. The controversy centers around the proposal's shift from the current necessity of node validation to a model where such validation might be deemed unnecessary or optional, essentially relying solely on Simplified Payment Verification (SPV). This approach implies a fundamental change in the trust model of Bitcoin, transitioning it towards trusting a central authority or major hash power, without sufficient checks by the economic majority of the network.

The discourse highlights concerns about the efficacy and risks associated with such a shift. The reliance on SPV without additional validation checks is critiqued for potentially allowing greater control over transaction validity by those with majority hash power, without adequate verification by the broader network. This could undermine the decentralized ethos of Bitcoin, where trust is distributed across a wide array of independently validating nodes rather than centralized. Furthermore, the proposal, if implemented, would not necessitate changes to existing wallets but would place the onus of discovering any trust violations on retrospective validation processes. This might lead to situations where transactions are assumed valid until proven otherwise, thereby wasting resources on validations based on incorrect assumptions and jeopardizing transaction integrity until corrections are made.

Moreover, the dialogue reflects a broader skepticism towards moving away from established community protocols that emphasize rigorous validation, towards more trust-dependent approaches. These approaches are flagged as particularly risky in the context of Bitcoin’s operational and security frameworks, which rely heavily on the absence of trust as a core principle. The ongoing conversation underscores the need for careful consideration of any alterations to how Bitcoin transactions are validated to avoid compromising the system’s integrity and user trust. The contention also points out operational challenges like the lengthy time required to sync nodes and Electrum servers, although these are identified as solvable problems without needing to overhaul the foundational validation mechanisms of Bitcoin.