From: nopara73 <adam.ficsor73@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [bitcin-dev] BIP157 Filter Type Extensibility Proposal for Combinations
Date: Fri, 28 Feb 2020 15:37:14 +0100 [thread overview]
Message-ID: <CAEPKjgdmZEU75uM6EtCD2Ut55dmnoXRHtEK_UsfnK6QUtPWtMA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
BIP157 defines a section called "Filter Types" (
https://github.com/bitcoin/bips/blob/master/bip-0157.mediawiki#filter-types
)
> For the sake of future extensibility and reducing filter sizes, there
are multiple *filter types* that determine which data is included in a
block filter as well as the method of filter construction/querying. In this
model, full nodes generate one filter per block per filter type supported.
> Each type is identified by a one byte code, and specifies the contents
and serialization format of the filter. A full node MAY signal support for
particular filter types using service bits. The initial filter types are
defined separately in BIP 158
<https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki>, and one
service bit is allocated to signal support for them.
While it provides a way to extend to multiple filter types, it does not
provide a way to extend to filter type combinations. Such combinations are
possible if the filter types would have to be defined with the power of
two: 1, 2, 4, 8, 16..., so every octet of a byte array could denote a
specific filter type, this way we could be able to signal for any number of
combinations of those filter types.
Originally this idea is described in more details and with code here:
https://github.com/bitcoin/bitcoin/issues/18221
MarcoFalke suggested for me to submit it to the mailing list instead of a
GitHub issue then propose an update to the BIP if consensus is reached.
--
Best,
Ádám
[-- Attachment #2: Type: text/html, Size: 3283 bytes --]
reply other threads:[~2020-02-28 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAEPKjgdmZEU75uM6EtCD2Ut55dmnoXRHtEK_UsfnK6QUtPWtMA@mail.gmail.com \
--to=adam.ficsor73@gmail$(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