From: "admin@bitaps•com" <admin@bitaps•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Block Batch Filters for Light Clients (Jonas Schnelli)
Date: Sat, 12 Oct 2019 17:46:43 +0400 [thread overview]
Message-ID: <D8F63ECB-83D6-4F98-BEE3-4E467D8E2379@bitaps.com> (raw)
In-Reply-To: <mailman.4271.1570844414.8631.bitcoin-dev@lists.linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
Hi Jonas,
Let's review case when we create filters for part of mempool or whole mempool.
After new block is mined we have to verify what transactions is confirmed from mempool. Mempool filter in design with set of transactions make impossible use it do block filter reconstruction because we have no mapping filter elements with transactions.
This means that we need to download block filter to check what exactly transactions are affected.
Which does not give us advantages in terms of traffic savings.
The idea of draft for mempool transactions filters is make possible to reconstruct correct block filters using unconfirmed tx filters and archive additional savings.
At this moment I am working on Block Batch Filters implementation and have same changes which will be updated in drafts as soon as I complete all tests. Regarding unconfirmed TX filters, I came to the conclusion that the filter
should be the first 6 bytes of the address hash, this takes up a bit more space, but allows to construct block filter.
What do you mean by fingerprinting defence ?
Please let me know what, in your opinion, are the disadvantages of the per tx filter approach?
Why use whole/part mempool is better?
With regards Aleksey
> 12 окт. 2019 г., в 5:40, bitcoin-dev-request@lists•linuxfoundation.org написал(а):
>
> Re: Block Batch Filters for Light Clients (Jonas Schnelli)
[-- Attachment #2: Type: text/html, Size: 2954 bytes --]
parent reply other threads:[~2019-10-12 13:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.4271.1570844414.8631.bitcoin-dev@lists.linuxfoundation.org>]
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=D8F63ECB-83D6-4F98-BEE3-4E467D8E2379@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