{"type":"rich","version":"1.0","author_name":"npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet","author_url":"https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2018-06-01\n📝 Original message:On Fri, Jun 1, 2018 at 2:52 AM, Olaoluwa Osuntokun via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e One notable thing that I left off is the proposed change to use the previous\n\u003e output script rather than the outpoint. Modifying the filters in this\n\u003e fashion would be a downgrade in the security model for light clients, as it\n\nOnly if you make a very strong assumption about the integrity of the\nnodes the client is talkign to. A typical network attacker (e.g.\nsomeone on your lan or wifi segmet, or someone who has compromised or\noperates an upstream router) can be all of your peers.\n\nThe original propsal for using these kinds of maps was that their\ndigests could eventually be commited and then checked against the\ncommitment, matching the same general security model used otherwise in\nSPV.\n\nUnfortunately, using the scripts instead of the outpoints takes us\nfurther away from a design that is optimized for committing (or, for\nthat matter, use purely locally by a wallet)..."}