<div dir="ltr"><div dir="ltr">Thank you for all your comments. To sum up: <br><br>- There were no comments related to the implementation details.<br>- There are concerns about this may incentivize users to use copypaste functionality extensively.<br>- 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.</div><div dir="ltr">- The rest of the conversation was about crypto hijackers, which I think is off topic in this thread.<br><br>Finally I'd like to note, there's already a work in progress implementation in Wasabi: <a href="https://github.com/zkSNACKs/WalletWasabi/pull/825">https://github.com/zkSNACKs/WalletWasabi/pull/825</a></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Nov 9, 2018 at 1:14 AM Dmitry Petukhov via bitcoin-dev <<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> > Do you know any reasonably convenient mechanism for end user to<br>
> > transfer an address from, say, a web page to the wallet address<br>
> > input field ? <br>
> <br>
> - QR code scanning of a Bitcoin URI<br>
> - On Android: A "bitcoin:" URI intent or a BIP70 payment message<br>
> intent<br>
> - On desktop OSes there are similar mechanisms to launch Apps from the<br>
> browser (e.g. for mailto: links)<br>
<br>
This works if the author of the web page thought about this, and<br>
created appropriate liks/qr codes. In many cases, addresses are<br>
just presented for users as text, to copy.<br>
<br>
People also send addresses in message apps and emails. Maybe if<br>
applications start to autodetect bitcoin addresses and convert them to<br>
bitcoin: links, there will be less need to copy-paste. But I suspect<br>
that this feature will not be quickly adopted by applications.<br>
<br>
> For cases where the payee is a well-known entity the BIP70 payment<br>
> protocol has authentication via certificates. That doesn't work for<br>
> the "the person in front of you is the only trust anchor you have"<br>
> usecase though.<br>
<br>
There are also BIP75 and BIP47 that may help, but the number of wallets<br>
that support these protocols is small (I think in part because of<br>
relative complexity of these protocols).<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div><span style="font-size:13.3333339691162px">Best,<br>Ádám</span></div></div></div></div></div></div></div></div>