Author: Riccardo Casatta 2018-05-18 08:46:29
Published on: 2018-05-18T08:46:29+00:00
In a recent bitcoin-dev mailing list, the false positive rate parameter was discussed which heavily affects filter size. The false positive rate is empirically set to 2^-20, but it is not clear how the parameter has been selected and optimized for the number of elements to search for which the filter has been optimized for. A go code was shared in the BIP recall, but the user found it hard to understand and run. They requested more details on the process, including charts and explanations.The user believes that choosing a higher alpha would shrink the total filter size by gigabytes at the cost of having to wastefully download just some megabytes of blocks. Matt Corallo suggested that there is almost no reason why one would not be able to filter for the set of output scripts in a transaction one knows about. Gregory Maxwell added that making input prevouts filter based on the scriptpubkey being spent could eliminate the multiple data type mixing entirely.
Updated on: 2023-06-13T02:29:12.401682+00:00