BIP Proposal: Compact Client Side Filtering for Light Clients



Summary:

The use of BIP37 in Bitcoin transactions has been debated several times. Several methods of private filtering have been suggested, including not filtering unconfirmed transactions at all. The author suggests that there is very little use of BIP37 at present based on incoming connections to nodes. Sending just the output addresses of each transaction would use about 1 kilobit/s of data, while sending the entire transaction would use ~14kbit/sec data. This seems like a sustainable amount of data to use while an application is running. SPV wallets are highly vulnerable to unconfirmed transactions and many become corrupted once given a fake transaction.The author questions whether saving no more than the figures mentioned above would justify the near total loss of privacy that filtering gives. The argument that "they already do it" is not a good justification for a new protocol feature. Things which already use BIP37 will presumably continue to do so.


Updated on: 2023-05-20T02:40:23.863707+00:00