Andreas Schildbach [ARCHIVE] on Nostr: 📅 Original date posted:2018-04-13 📝 Original message:Anton, a developer on the ...
📅 Original date posted:2018-04-13
📝 Original message:Anton, a developer on the bitcoinj maiing list, recently made me aware
[1] of a compatibility issue between segwit and BIP37 (Bloom Filtering).
The issue affects only P2WPKH and the special case of transactions
without change outputs (such as when emptying a wallet). In this case,
neither inputs not outputs contain any data elements that would cause a
match for the filter. The public key, which would match, goes to the
witness but not to the input.
My suggestion was to include an OP_RETURN output with a matching public
key in such transactions. Anton confirmed that this workaround is indeed
working. But of course it nullifies some of the segwit's size improvements.
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?
[1]
https://groups.google.com/d/msg/bitcoinj/SJpLgjowc1I/V7u2BavvAwAJPublished at
2023-06-07 18:11:38Event JSON
{
"id": "4d99c64342358c7c5b6e9d364a8f081f1d9fd3ff0fa8bff56637396a9a2e83d6",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686161498,
"kind": 1,
"tags": [
[
"e",
"431675dd201d4efe08b3fd18d9592208d5d38c3979f48e659b5f87d005a1a5a5",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2018-04-13\n📝 Original message:Anton, a developer on the bitcoinj maiing list, recently made me aware\n[1] of a compatibility issue between segwit and BIP37 (Bloom Filtering).\n\nThe issue affects only P2WPKH and the special case of transactions\nwithout change outputs (such as when emptying a wallet). In this case,\nneither inputs not outputs contain any data elements that would cause a\nmatch for the filter. The public key, which would match, goes to the\nwitness but not to the input.\n\nMy suggestion was to include an OP_RETURN output with a matching public\nkey in such transactions. Anton confirmed that this workaround is indeed\nworking. But of course it nullifies some of the segwit's size improvements.\n\nI wonder if Bitcoin Core would be willing to extend the BIP37 matching\nrules such that data elements in the witness are also matched against?\n\n\n[1] https://groups.google.com/d/msg/bitcoinj/SJpLgjowc1I/V7u2BavvAwAJ",
"sig": "57b8a999142c0bdc59ad8044ca00c1ee6fc96539f7a134e25c810f1b0ed875920936b40a2e64fb69d8f7fd138571ad1ac450652dd8fc326fabb56a48fc267f98"
}