From: "admin@bitaps•com" <admin@bitaps•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Block Batch Filters for Light Clients
Date: Tue, 24 Sep 2019 17:36:26 +0400 [thread overview]
Message-ID: <4A9A0892-54E9-42DB-8D2E-E090E431D9E4@bitaps.com> (raw)
In-Reply-To: <mailman.22.1569240010.14875.bitcoin-dev@lists.linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Last version updated draft
https://github.com/bitaps-com/bips/blob/master/bip-block-batch-filters.mediawiki <https://github.com/bitaps-com/bips/blob/master/bip-block-batch-filters.mediawiki>
Summary changes:
- return back to Golomb coding
- implemented more simple and effective shema
- Total filters size is smaller then BIP 158 at all total estimated savings more than 20% (exactly info will be soon)
- filter is deterministic and could be committed as commitment in coinbase transaction in future
- flexible GCS parameters to to maintain the necessary FPS
- spliting filter for 2 parts: unique elements and duplicated elements
- duplicated elements could be encoded more effective
Open questions:
- Optimal range for batch?
- Why we need sip has instead of just use first 64 bits from pub key/script hash?
- Downloading unique/duplicated elements separately? Just add filter types for these purposes?
Thanks for any feedback or discussions
Aleksey Karpov
[-- Attachment #2: Type: text/html, Size: 1663 bytes --]
next parent reply other threads:[~2019-09-24 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.22.1569240010.14875.bitcoin-dev@lists.linuxfoundation.org>
2019-09-24 13:36 ` admin [this message]
2019-09-28 17:21 ` admin
2019-10-11 15:44 ` Jonas Schnelli
2019-09-19 17:20 admin
2019-09-21 21:16 ` Tamas Blummer
2019-09-23 5:20 ` nopara73
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=4A9A0892-54E9-42DB-8D2E-E090E431D9E4@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