From: "admin@bitaps•com" <admin@bitaps•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Block Batch Filters for Light Clients
Date: Thu, 19 Sep 2019 21:20:13 +0400 [thread overview]
Message-ID: <236E3AB2-4035-4F51-84EE-6F7F57298777@bitaps.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
Hello list,
Here is a link for a draft of a BIP for compact probabilistic block filters alternative of BIP 158
https://docs.google.com/document/d/1jH9tEUyb9w2OZd4-kxfGuyNIIZzmgkEb_z0qSxv80ik/edit?usp=sharing <https://docs.google.com/document/d/1jH9tEUyb9w2OZd4-kxfGuyNIIZzmgkEb_z0qSxv80ik/edit?usp=sharing>
Summary:
- BIP 158 false positive rate is low, we can achieve lower bandwidth with higher false positive rate filter while sync blockchain
- BIP 158 not do not support filter batching by design of used parameters for siphash and Golomb coding optimal parameters
- Alternative compression with delta coding and splitting data to 2 bit string sequences. First for data without prefixes, second one for information about bit length written to first sequence.
Second sequence have a lot of duplicates, compressed with 2 round of Huffman algorithm. (Effectivity about 98% vs Golomb with optimal parameters)
- Block filters batching reduce filter size significantly
- Separation of filters by address type allows lite client not to download redundant information without compromising privacy.
- Lite client filters download strategy: get biggest filter (smallest blocks/size rate) for blocks range, in case positive test -> get medium filters to reduce blocks range -> get block filters for affected range -> download affected blocks over TOR
Implementation (python): https://github.com/bitaps-com/pybtc/blob/bugfix/pybtc/functions/filters.py#L172 <https://github.com/bitaps-com/pybtc/blob/bugfix/pybtc/functions/filters.py#L172>
Exactly information from mainnet about size for separated filters by address types and batch size will be added within few days.
Thanks for any feedback.
Aleksey Karpov
[-- Attachment #2: Type: text/html, Size: 2818 bytes --]
next reply other threads:[~2019-09-19 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 17:20 admin [this message]
2019-09-21 21:16 ` Tamas Blummer
2019-09-23 5:20 ` nopara73
[not found] <mailman.22.1569240010.14875.bitcoin-dev@lists.linuxfoundation.org>
2019-09-24 13:36 ` admin
2019-09-28 17:21 ` admin
2019-10-11 15:44 ` Jonas Schnelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=236E3AB2-4035-4F51-84EE-6F7F57298777@bitaps.com \
--to=admin@bitaps$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox