đź“… Original date posted:2018-04-13
đź“ť Original message: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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180413/cedc5780/attachment.html>;
Jim Posen [ARCHIVE] /
npub1nc…lqt2n
2023-06-07 18:11:39
in reply to nevent1q…x5x7
Author Public Key
npub1ncnj8arudstdxzfhxk7k4nwgkrw3hyw8sgt0wqqmm5hh2c4knmgs2lqt2nPublished at
2023-06-07 18:11:39Event JSON
{
"id": "086b822782f2c6081529691f91438cb227c3586abad683f880c3abcbb8d4ee62",
"pubkey": "9e2723f47c6c16d3093735bd6acdc8b0dd1b91c78216f7001bdd2f7562b69ed1",
"created_at": 1686161499,
"kind": 1,
"tags": [
[
"e",
"431675dd201d4efe08b3fd18d9592208d5d38c3979f48e659b5f87d005a1a5a5",
"",
"root"
],
[
"e",
"047f80060a68148582f2c1729b4fce51bf14f68f8c94f1e1c31e48d13146fd5a",
"",
"reply"
],
[
"p",
"9a463e0fab8963b013698c15a0f2449d19c97f3b88458e5874095b5006df9a0c"
]
],
"content": "📅 Original date posted:2018-04-13\n📝 Original message:Why not add the outpoints owned by the wallet to the filter and watch for\nthose instead of elements in the input script or witness data?\n\nOn Fri, Apr 13, 2018 at 12:12 PM, Jonas Schnelli via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Hi Andreas\n\u003e\n\u003e Thanks for bringing this up and this seems indeed to be suboptimal.\n\u003e\n\u003e \u003e I wonder if Bitcoin Core would be willing to extend the BIP37 matching\n\u003e \u003e rules such that data elements in the witness are also matched against?\n\u003e\n\u003e Bitcoin Core is not an identity that can be „willing to extend“ (or\n\u003e reject) a feature.\n\u003e Someone needs to come up with a proposal (pull request).\n\u003e\n\u003e Maybe an extension for BIP37 would make sense (*meh*).\n\u003e Just inserting the witness data into the bloom filter seems to be an easy\n\u003e solution (CBloomFilter::IsRelevantAndUpdate())\n\u003e\n\u003e /jonas\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180413/cedc5780/attachment.html\u003e",
"sig": "50a1e529cca3f3be7c65d3f6adf957ea57cdb81f23c05a2577c467f373a9e8ab6f24635d7ba158face68e2c1be24c8435ac47175fb087090f60da5eb7cce808c"
}