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@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@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@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


--
Best,
Ádám
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev