đź“… Original date posted:2017-06-19
đź“ť Original message:On 06/19/2017 05:49 PM, Jonas Schnelli via bitcoin-dev wrote:
>>> It's been debated if [filtering of] unconfirmed transactions are
>>> necessary,
>>
>> Why would it not be needed? Any SPV client (when used as a payment-receiver)
>> requires this from a simple usability point of view.
>
>
> I think many users would be willing ...
> a) … to trade higher privacy (using client side filtering) for not having the „incoming transaction“ feature
> b) – if they want 0-conf – to fetch all inved transactions
Another number: I'm answering dozens of support inquiries about
delayed/missing transactions per day. Over the 7 years of Bitcoin
Wallet's existence, I estimate about 50000 inquiries.
On the other hand, I remember only 1 (one) inquiry about the privacy
problems of BIP37 (or privacy at all).
>From a regular user's point of view, privacy is non-issue. Sure,
everyone would take it for free, but certainly not if it a) delays
incoming payments or b) quickly eats up your traffic quota.
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 18:02:11
in reply to nevent1q…25h6
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 18:02:11Event JSON
{
"id": "a67f2150be7ffbc17429248affc8dd6071084b1ecf23a2ae5286cae676f8f0dc",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686160931,
"kind": 1,
"tags": [
[
"e",
"55a56c7ebba05dd9613a9ae00ae6d5bbfa4f7fd0155fa447a7d09d61ff658a4b",
"",
"root"
],
[
"e",
"3e0f16d7d47778c10fb73b98a059988f927758c342cae96d9c97618b591f5a51",
"",
"reply"
],
[
"p",
"9a463e0fab8963b013698c15a0f2449d19c97f3b88458e5874095b5006df9a0c"
]
],
"content": "📅 Original date posted:2017-06-19\n📝 Original message:On 06/19/2017 05:49 PM, Jonas Schnelli via bitcoin-dev wrote:\n\n\u003e\u003e\u003e It's been debated if [filtering of] unconfirmed transactions are\n\u003e\u003e\u003e necessary,\n\u003e\u003e\n\u003e\u003e Why would it not be needed? Any SPV client (when used as a payment-receiver)\n\u003e\u003e requires this from a simple usability point of view.\n\u003e \n\u003e \n\u003e I think many users would be willing ...\n\u003e a) … to trade higher privacy (using client side filtering) for not having the „incoming transaction“ feature\n\u003e b) – if they want 0-conf – to fetch all inved transactions\n\nAnother number: I'm answering dozens of support inquiries about\ndelayed/missing transactions per day. Over the 7 years of Bitcoin\nWallet's existence, I estimate about 50000 inquiries.\n\nOn the other hand, I remember only 1 (one) inquiry about the privacy\nproblems of BIP37 (or privacy at all).\n\n\u003eFrom a regular user's point of view, privacy is non-issue. Sure,\neveryone would take it for free, but certainly not if it a) delays\nincoming payments or b) quickly eats up your traffic quota.",
"sig": "fda6918b4f373deab59be534619144d272b8aebfda2bbf371b753c9b37426b66087d3ce750b128dd01639ab23bddae69eb8fede53487d7a36434cfb7ff309c9b"
}