📅 Original date posted:2018-05-17
📝 Original message:Yea I generally would really prefer something like that but it
significantly complicates the download logic - currently clients can
easily cross-check a filter in case they differ between providers by
downloading the block. If we instead went with the script being spent
they would have to be provided all previous transactions (potentially
compressed via midstate) as well, making it potentially infeasible to
identify the offending node while remaining a lightweight client. Maybe
there is some other reasonable download logic to replace it with, however.
Matt
On 05/17/18 12:36, Gregory Maxwell wrote:
> On Thu, May 17, 2018 at 3:25 PM, Matt Corallo via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>> I believe (1) could be skipped entirely - there is almost no reason why
>> you'd not be able to filter for, eg, the set of output scripts in a
>> transaction you know about
>
> I think this is convincing for the txids themselves.
>
> What about also making input prevouts filter based on the scriptpubkey
> being _spent_? Layering wise in the processing it's a bit ugly, but
> if you validated the block you have the data needed.
>
> This would eliminate the multiple data type mixing entirely.
>
Matt Corallo [ARCHIVE] /
npub1e4…jxmcu
2023-06-07 18:12:11
in reply to nevent1q…e92t
Author Public Key
npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcuPublished at
2023-06-07 18:12:11Event JSON
{
"id": "d1a03868ae374685b3960c14e0d347932e2690c23d5c677c01eb9d518c8c30ed",
"pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba",
"created_at": 1686161531,
"kind": 1,
"tags": [
[
"e",
"aefee7e3913729b7ef736d47c6f2a24954de10011f27b89dcaeaac62c51b6a6f",
"",
"root"
],
[
"e",
"52d3c4ce76bdd7f57bb870f9e5251a886c47a0566f36b759031a4022ece3b727",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2018-05-17\n📝 Original message:Yea I generally would really prefer something like that but it\nsignificantly complicates the download logic - currently clients can\neasily cross-check a filter in case they differ between providers by\ndownloading the block. If we instead went with the script being spent\nthey would have to be provided all previous transactions (potentially\ncompressed via midstate) as well, making it potentially infeasible to\nidentify the offending node while remaining a lightweight client. Maybe\nthere is some other reasonable download logic to replace it with, however.\n\nMatt\n\nOn 05/17/18 12:36, Gregory Maxwell wrote:\n\u003e On Thu, May 17, 2018 at 3:25 PM, Matt Corallo via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e I believe (1) could be skipped entirely - there is almost no reason why\n\u003e\u003e you'd not be able to filter for, eg, the set of output scripts in a\n\u003e\u003e transaction you know about\n\u003e \n\u003e I think this is convincing for the txids themselves.\n\u003e \n\u003e What about also making input prevouts filter based on the scriptpubkey\n\u003e being _spent_? Layering wise in the processing it's a bit ugly, but\n\u003e if you validated the block you have the data needed.\n\u003e \n\u003e This would eliminate the multiple data type mixing entirely.\n\u003e",
"sig": "e8cf82b8816457870a6274105984dddad579f7b98498b1f4c49fc15aa268f64db026a7c58d9de90872de4cbcb4b2e3484f4ea653e6abdd892420a8597e719ef9"
}