📅 Original date posted:2017-01-03
📝 Original message:The concept combined with the weak blocks system where miners commit
to potential transaction inclusion with fractional difficulty blocks
is possible. I'm not personally convinced that unconfirmed transaction
display in a wallet is worth the privacy trade-off. The user has very
little to gain from this knowledge until the txn is in a block.
On 2017-01-01 13:01, Jonas Schnelli via bitcoin-dev wrote:
> Hi
>> We introduce several concepts that rework the lightweight Bitcoin
>> client model in a manner which is secure, efficient and privacy
>> compatible.
>>
>> The BFD can be used verbatim in replacement of BIP37, where the filter
>> can be cached between clients without needing to be recomputed. It can
>> also be used by normal pruned nodes to do re-scans locally of their
>> wallet without needing to have the block data available to scan, or
>> without reading the entire block chain from disk.
> I started exploring the potential of BFD after this specification.
>
> What would be the preferred/recommended way to handle 0-conf/mempool
> filtering – if & once BDF would have been deployed (any type,
> semi-trusted oracles or protocol-level/softfork)?
>
> From the user-experience perspective, this is probably pretty important
> (otherwise the experience will be that incoming funds can take serval
> minutes to hours until they appear).
> Using BIP37 bloom filters just for mempool filtering would obviously
> result in the same unwanted privacy-setup.
>
> </jonas>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
bfd at cock.lu [ARCHIVE] /
npub1md…gy6y7
2023-06-07 17:55:03
in reply to nevent1q…clxu
Author Public Key
npub1mdmqmt0prpddcexkljfzd40uf7nvrc56c7gsg2spn3lgcjghguxqwgy6y7Published at
2023-06-07 17:55:03Event JSON
{
"id": "17f1968c91ed95770c18f643e558efec2286bc12275c5e221c488083fd933984",
"pubkey": "db760dade1185adc64d6fc9226d5fc4fa6c1e29ac791042a019c7e8c4917470c",
"created_at": 1686160503,
"kind": 1,
"tags": [
[
"e",
"12de089a3e4ccbe31128a134586c26b5a984bf25231ca8b54e0116dac53ecb14",
"",
"root"
],
[
"e",
"4a65296174697bf2a013b81ea5e9ef5fbfb5349aae6df19e3151d6540e3c0549",
"",
"reply"
],
[
"p",
"9a463e0fab8963b013698c15a0f2449d19c97f3b88458e5874095b5006df9a0c"
]
],
"content": "📅 Original date posted:2017-01-03\n📝 Original message:The concept combined with the weak blocks system where miners commit\nto potential transaction inclusion with fractional difficulty blocks\nis possible. I'm not personally convinced that unconfirmed transaction\ndisplay in a wallet is worth the privacy trade-off. The user has very\nlittle to gain from this knowledge until the txn is in a block.\n\n\nOn 2017-01-01 13:01, Jonas Schnelli via bitcoin-dev wrote:\n\u003e Hi\n\u003e\u003e We introduce several concepts that rework the lightweight Bitcoin\n\u003e\u003e client model in a manner which is secure, efficient and privacy\n\u003e\u003e compatible.\n\u003e\u003e \n\u003e\u003e The BFD can be used verbatim in replacement of BIP37, where the filter\n\u003e\u003e can be cached between clients without needing to be recomputed. It can\n\u003e\u003e also be used by normal pruned nodes to do re-scans locally of their\n\u003e\u003e wallet without needing to have the block data available to scan, or\n\u003e\u003e without reading the entire block chain from disk.\n\u003e I started exploring the potential of BFD after this specification.\n\u003e \n\u003e What would be the preferred/recommended way to handle 0-conf/mempool\n\u003e filtering – if \u0026 once BDF would have been deployed (any type,\n\u003e semi-trusted oracles or protocol-level/softfork)?\n\u003e \n\u003e From the user-experience perspective, this is probably pretty important\n\u003e (otherwise the experience will be that incoming funds can take serval\n\u003e minutes to hours until they appear).\n\u003e Using BIP37 bloom filters just for mempool filtering would obviously\n\u003e result in the same unwanted privacy-setup.\n\u003e \n\u003e \u003c/jonas\u003e\n\u003e \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",
"sig": "e2d4b3b0c51823a4552a9e609b75dfbe9e2766405eadbf17ff84be2c387b831c82b2d643ceb224fb549f9cff3946a1624e75b4a7f8c245910b5737e44c765e7a"
}