📅 Original date posted:2018-12-01
📝 Original message:I liked the cheekiness of your summary, Adam ;)
I'm not sure why this needs to be a BIP. It is a UX detail--not really
related to bitcoin protocol or procedures. I wouldn't even call it a
description of best practices, since every product's use case is going to
be different.
If you think there is a compelling reason for why this needs to be a
documented standard, please elaborate!
Thanks,
James
On Sun, Nov 11, 2018 at 7:41 PM Adam Ficsor via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> Thank you for all your comments. To sum up:
>
> - There were no comments related to the implementation details.
> - There are concerns about this may incentivize users to use copypaste
> functionality extensively.
> - A counter argument was made that crypto hijackers use the clipboard,
> because that is the most convenient thing to hijack, not because they can
> only hijack that and, if Bitcoin users would move to other ways of
> specifying destinations, that may end up being just as an issue, too.
> - The rest of the conversation was about crypto hijackers, which I think
> is off topic in this thread.
>
> Finally I'd like to note, there's already a work in progress
> implementation in Wasabi:
> https://github.com/zkSNACKs/WalletWasabi/pull/825
>
> On Fri, Nov 9, 2018 at 1:14 AM Dmitry Petukhov via bitcoin-dev <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>>
>> > > Do you know any reasonably convenient mechanism for end user to
>> > > transfer an address from, say, a web page to the wallet address
>> > > input field ?
>> >
>> > - QR code scanning of a Bitcoin URI
>> > - On Android: A "bitcoin:" URI intent or a BIP70 payment message
>> > intent
>> > - On desktop OSes there are similar mechanisms to launch Apps from the
>> > browser (e.g. for mailto: links)
>>
>> This works if the author of the web page thought about this, and
>> created appropriate liks/qr codes. In many cases, addresses are
>> just presented for users as text, to copy.
>>
>> People also send addresses in message apps and emails. Maybe if
>> applications start to autodetect bitcoin addresses and convert them to
>> bitcoin: links, there will be less need to copy-paste. But I suspect
>> that this feature will not be quickly adopted by applications.
>>
>> > For cases where the payee is a well-known entity the BIP70 payment
>> > protocol has authentication via certificates. That doesn't work for
>> > the "the person in front of you is the only trust anchor you have"
>> > usecase though.
>>
>> There are also BIP75 and BIP47 that may help, but the number of wallets
>> that support these protocols is small (I think in part because of
>> relative complexity of these protocols).
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
>
> --
> Best,
> Ádám
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20181130/37af33c4/attachment.html>;
James MacWhyte [ARCHIVE] /
npub12t…pye9h
2023-06-07 18:15:25
in reply to nevent1q…y8cs
Author Public Key
npub12tjaqer27049ejmvf0f3yd7kq6p93gg6ecavgrczge4rlzf59y5q2pye9hPublished at
2023-06-07 18:15:25Event JSON
{
"id": "759440e6f1893feba4f2113e9c18604870e26dc328dbea068a7a69328709b41f",
"pubkey": "52e5d0646af3ea5ccb6c4bd31237d6068258a11ace3ac40f02466a3f89342928",
"created_at": 1686161725,
"kind": 1,
"tags": [
[
"e",
"24cc78fa2f0ca63b79f6fdcfb02e0c0c7d14acaf3cb3112d9e1dbb6a745d3f4d",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2018-12-01\n📝 Original message:I liked the cheekiness of your summary, Adam ;)\n\nI'm not sure why this needs to be a BIP. It is a UX detail--not really\nrelated to bitcoin protocol or procedures. I wouldn't even call it a\ndescription of best practices, since every product's use case is going to\nbe different.\n\nIf you think there is a compelling reason for why this needs to be a\ndocumented standard, please elaborate!\n\nThanks,\nJames\n\n\nOn Sun, Nov 11, 2018 at 7:41 PM Adam Ficsor via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Thank you for all your comments. To sum up:\n\u003e\n\u003e - There were no comments related to the implementation details.\n\u003e - There are concerns about this may incentivize users to use copypaste\n\u003e functionality extensively.\n\u003e - A counter argument was made that crypto hijackers use the clipboard,\n\u003e because that is the most convenient thing to hijack, not because they can\n\u003e only hijack that and, if Bitcoin users would move to other ways of\n\u003e specifying destinations, that may end up being just as an issue, too.\n\u003e - The rest of the conversation was about crypto hijackers, which I think\n\u003e is off topic in this thread.\n\u003e\n\u003e Finally I'd like to note, there's already a work in progress\n\u003e implementation in Wasabi:\n\u003e https://github.com/zkSNACKs/WalletWasabi/pull/825\n\u003e\n\u003e On Fri, Nov 9, 2018 at 1:14 AM Dmitry Petukhov via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e\n\u003e\u003e \u003e \u003e Do you know any reasonably convenient mechanism for end user to\n\u003e\u003e \u003e \u003e transfer an address from, say, a web page to the wallet address\n\u003e\u003e \u003e \u003e input field ?\n\u003e\u003e \u003e\n\u003e\u003e \u003e - QR code scanning of a Bitcoin URI\n\u003e\u003e \u003e - On Android: A \"bitcoin:\" URI intent or a BIP70 payment message\n\u003e\u003e \u003e intent\n\u003e\u003e \u003e - On desktop OSes there are similar mechanisms to launch Apps from the\n\u003e\u003e \u003e browser (e.g. for mailto: links)\n\u003e\u003e\n\u003e\u003e This works if the author of the web page thought about this, and\n\u003e\u003e created appropriate liks/qr codes. In many cases, addresses are\n\u003e\u003e just presented for users as text, to copy.\n\u003e\u003e\n\u003e\u003e People also send addresses in message apps and emails. Maybe if\n\u003e\u003e applications start to autodetect bitcoin addresses and convert them to\n\u003e\u003e bitcoin: links, there will be less need to copy-paste. But I suspect\n\u003e\u003e that this feature will not be quickly adopted by applications.\n\u003e\u003e\n\u003e\u003e \u003e For cases where the payee is a well-known entity the BIP70 payment\n\u003e\u003e \u003e protocol has authentication via certificates. That doesn't work for\n\u003e\u003e \u003e the \"the person in front of you is the only trust anchor you have\"\n\u003e\u003e \u003e usecase though.\n\u003e\u003e\n\u003e\u003e There are also BIP75 and BIP47 that may help, but the number of wallets\n\u003e\u003e that support these protocols is small (I think in part because of\n\u003e\u003e relative complexity of these protocols).\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\n\u003e\n\u003e\n\u003e --\n\u003e Best,\n\u003e Ádám\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\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20181130/37af33c4/attachment.html\u003e",
"sig": "e7ada40939866fc28dfb0ff246b173ab2acabab19a3c0d564d041e56b35469805b054fcd0b870f2655b88c0707fd16134a09642d4c62aed9f506ef09575dfe97"
}