📅 Original date posted:2018-04-14 📝 Original message:To Christian's point about ...

Jim Posen [ARCHIVE] /

npub1ncn…qt2n

2023-06-07 18:11:39

in reply to nevent1q…3tgl

📅 Original date posted:2018-04-14
📝 Original message:To Christian's point about privacy, I'll take this opportunity to
shamelessly review beg on https://github.com/bitcoin/bitcoin/pull/12254,
the PR for BIP 158 implementation (but not 157).

On Sat, Apr 14, 2018 at 9:14 AM, Christian Decker <
decker.christian at gmail.com> wrote:

> Note that this would compound the privacy leak that Jonas Nick used to
> identify address clusters via the bloom filters in one of his publications.
> By reducing the false positives when matching you can get very detailed
> clusters. Then again we know that bloom filters aren't good for privacy
> anyway, so this might be a non-issue.
>
> On Sat, Apr 14, 2018, 00:17 Jim Posen via bitcoin-dev <bitcoin-dev at lists.
> linuxfoundation.org> wrote:
>
>> Why not add the outpoints owned by the wallet to the filter and watch for
>> those instead of elements in the input script or witness data?
>>
>> On Fri, Apr 13, 2018 at 12:12 PM, Jonas Schnelli via bitcoin-dev <
>> bitcoin-dev at lists.linuxfoundation.org> wrote:
>>
>>> Hi Andreas
>>>
>>> Thanks for bringing this up and this seems indeed to be suboptimal.
>>>
>>> > I wonder if Bitcoin Core would be willing to extend the BIP37 matching
>>> > rules such that data elements in the witness are also matched against?
>>>
>>> Bitcoin Core is not an identity that can be „willing to extend“ (or
>>> reject) a feature.
>>> Someone needs to come up with a proposal (pull request).
>>>
>>> Maybe an extension for BIP37 would make sense (*meh*).
>>> Just inserting the witness data into the bloom filter seems to be an
>>> easy solution (CBloomFilter::IsRelevantAndUpdate())
>>>
>>> /jonas
>>>
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev at lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>
>>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180414/085832a7/attachment.html>;

Author Public Key

npub1ncnj8arudstdxzfhxk7k4nwgkrw3hyw8sgt0wqqmm5hh2c4knmgs2lqt2n

Show more details

Published at

2023-06-07 18:11:39

Kind type

1 Short Text Note

Event JSON

{ "id": "681c929338c74075fb9a94b9c5fca18dd15444283e3a4405c297f258a4a6df57", "pubkey": "9e2723f47c6c16d3093735bd6acdc8b0dd1b91c78216f7001bdd2f7562b69ed1", "created_at": 1686161499, "kind": 1, "tags": [ [ "e", "431675dd201d4efe08b3fd18d9592208d5d38c3979f48e659b5f87d005a1a5a5", "", "root" ], [ "e", "31d929d3401c6a01f7f4581d1d764837ded339483a22e0bdfbc12376dc33cfcc", "", "reply" ], [ "p", "72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057" ] ], "content": "📅 Original date posted:2018-04-14\n📝 Original message:To Christian's point about privacy, I'll take this opportunity to\nshamelessly review beg on https://github.com/bitcoin/bitcoin/pull/12254,\nthe PR for BIP 158 implementation (but not 157).\n\nOn Sat, Apr 14, 2018 at 9:14 AM, Christian Decker \u003c\ndecker.christian at gmail.com\u003e wrote:\n\n\u003e Note that this would compound the privacy leak that Jonas Nick used to\n\u003e identify address clusters via the bloom filters in one of his publications.\n\u003e By reducing the false positives when matching you can get very detailed\n\u003e clusters. Then again we know that bloom filters aren't good for privacy\n\u003e anyway, so this might be a non-issue.\n\u003e\n\u003e On Sat, Apr 14, 2018, 00:17 Jim Posen via bitcoin-dev \u003cbitcoin-dev at lists.\n\u003e linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e Why not add the outpoints owned by the wallet to the filter and watch for\n\u003e\u003e those instead of elements in the input script or witness data?\n\u003e\u003e\n\u003e\u003e On Fri, Apr 13, 2018 at 12:12 PM, Jonas Schnelli via bitcoin-dev \u003c\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e\n\u003e\u003e\u003e Hi Andreas\n\u003e\u003e\u003e\n\u003e\u003e\u003e Thanks for bringing this up and this seems indeed to be suboptimal.\n\u003e\u003e\u003e\n\u003e\u003e\u003e \u003e I wonder if Bitcoin Core would be willing to extend the BIP37 matching\n\u003e\u003e\u003e \u003e rules such that data elements in the witness are also matched against?\n\u003e\u003e\u003e\n\u003e\u003e\u003e Bitcoin Core is not an identity that can be „willing to extend“ (or\n\u003e\u003e\u003e reject) a feature.\n\u003e\u003e\u003e Someone needs to come up with a proposal (pull request).\n\u003e\u003e\u003e\n\u003e\u003e\u003e Maybe an extension for BIP37 would make sense (*meh*).\n\u003e\u003e\u003e Just inserting the witness data into the bloom filter seems to be an\n\u003e\u003e\u003e easy solution (CBloomFilter::IsRelevantAndUpdate())\n\u003e\u003e\u003e\n\u003e\u003e\u003e /jonas\n\u003e\u003e\u003e\n\u003e\u003e\u003e _______________________________________________\n\u003e\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\u003e\n\u003e\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180414/085832a7/attachment.html\u003e", "sig": "f9222d7e116d9a48fefa45acaaa7460aab7411d403561a2ba3b43a3aaca43224f9f468d7cce835a3f3008a09dd4229c93bf615ebc6456cee28d166767ab31944" }