Chris [ARCHIVE] on Nostr: 📅 Original date posted:2017-06-01 📝 Original message:On 06/01/2017 06:10 PM, ...
📅 Original date posted:2017-06-01
📝 Original message:On 06/01/2017 06:10 PM, Olaoluwa Osuntokun via bitcoin-dev wrote:
> One aspect which isn't in this BIP draft is direct support for unconfirmed
> transactions. I consider such a feature an important UX feature for mobile
> phones, and something which I've personally seen as an important
> UX-experience when on-boarding new users to Bitcoin.
Totally agree. My first thought is maybe you could keep bip37 filtering
as optional for unconfirmed transactions. Since you're only interested
in incoming transactions in this case you can create one big filter with
all your wallet's addresses and reuse that filter. The bip37 privacy
issues mainly come up when trying to get the filter to match both
incoming and outgoing transactions, which is not needed in this case.
Otoh, if you download the block from the same peer that you gave a bip37
filter then they could probably test the txs in the block against both
filters. :/
Published at
2023-06-07 18:02:05Event JSON
{
"id": "be82db6ddae1af9f7b25016ffb9d1d76c3907511f77fae9e7f50f09fb85e6d92",
"pubkey": "94ba46cdbb14c3443fcc2e1278b41ad6bc36a2d595149d6940652dab7e162523",
"created_at": 1686160925,
"kind": 1,
"tags": [
[
"e",
"55a56c7ebba05dd9613a9ae00ae6d5bbfa4f7fd0155fa447a7d09d61ff658a4b",
"",
"root"
],
[
"e",
"7c288b321529800e070d6b520ddaa7af528b81f8055a0863634bb7ce5dcdaf55",
"",
"reply"
],
[
"p",
"2df3fc2660459521b852c995d4fc1a93938389a5e085677d0ebb33ef92cc5476"
]
],
"content": "📅 Original date posted:2017-06-01\n📝 Original message:On 06/01/2017 06:10 PM, Olaoluwa Osuntokun via bitcoin-dev wrote:\n\n\u003e One aspect which isn't in this BIP draft is direct support for unconfirmed\n\u003e transactions. I consider such a feature an important UX feature for mobile\n\u003e phones, and something which I've personally seen as an important\n\u003e UX-experience when on-boarding new users to Bitcoin.\n\nTotally agree. My first thought is maybe you could keep bip37 filtering\nas optional for unconfirmed transactions. Since you're only interested\nin incoming transactions in this case you can create one big filter with\nall your wallet's addresses and reuse that filter. The bip37 privacy\nissues mainly come up when trying to get the filter to match both\nincoming and outgoing transactions, which is not needed in this case.\n\nOtoh, if you download the block from the same peer that you gave a bip37\nfilter then they could probably test the txs in the block against both\nfilters. :/",
"sig": "a9708f13bbe185d695a92cbe962b4e3c3ba4996b8aee2e2d859b4151d90d0e4b3091344a35625657a7928e111319f6a6037bc1f136b55a0dffc64c7ec0176c52"
}