path: root/b0/64941a31b44da4a7fc065b657ee20d2a6536cd

Return-Path: <adam.ficsor73@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id DB89D414
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 12 Nov 2018 03:24:08 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lj1-f194.google.com (mail-lj1-f194.google.com
	[209.85.208.194])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2655E710
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 12 Nov 2018 03:24:08 +0000 (UTC)
Received: by mail-lj1-f194.google.com with SMTP id z80-v6so6276532ljb.8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 11 Nov 2018 19:24:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to
	:cc; bh=SBhZCHOSJjFFPxYcPYx6EjhVUx6ls5Lg9t00DBTo1Tk=;
	b=XPhpH330rG8V0koTHaCM7VtN7WhOcgFv5Paom9/0f51C4AbtJ1GT8AJNIPDSl99F9m
	AtnhpUgDSUeJbqlwAbSM8Ry7MAfDdvNS8+nf64ukfWKLk+1spKN5AuKRm21BibGK2uW1
	8jRIHD1A9b8/JSZLo8Z8ChpUKbOTzc+MYSZ9lpuAzNDJxkmKhK+MiR2OP1CmTUTW/otU
	v2oVoMQM1caNgTAzCuruVJa1QZijxvnMgoXzqFwQoS7bhfeJXJECCZFo0CuAZeo5USKg
	N793TU/rKQX6GFr6GoTLIE4ifSvunyHBRrkbfuJA8NKvIwAJQyry8DO9eapXxVe8fAxe
	ZO/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:cc;
	bh=SBhZCHOSJjFFPxYcPYx6EjhVUx6ls5Lg9t00DBTo1Tk=;
	b=YKghCAH/gsO4COdB1qrXVkLWCwB3+KB2vZFxqXvFI/xfFdgwU4BEDfN1FAe0WuiXd9
	A2T7C8Xuzc/xPG7IDeofneeaEVsB2jN3EwfDm5uB5Bl9ICt7KmRQrknh9/qyifGji6gg
	TwanQYnC2qqtx4sfRaRGmoFep/1vJDZjLgmQ5HO1XSSfi/QKKrpXUtazlA8bfFtcNvNZ
	N+Iv70ptzRaOc5Cl5LMCqLbXRQpnicEjK4ARlj3JtP8w4zBvC8cZWXcElW17cSG/306C
	/gbqY95Co2tMDv75dSKsaFGWlR2jxZj0qKn7h5PAXq6BhNme7iVDZB2a8Py5tVgRDlpy
	j4vQ==
X-Gm-Message-State: AGRZ1gJeSjxw789nFsf+f4rqrB0/63DDJbgToZkORFeQd/Xn8wisFxAm
	SpBoNgnKsXDpsll/m/lH2oFZdXfSRafGGS5fRak=
X-Google-Smtp-Source: AJdET5duMIW7VcEl7CP76nBctipW2MUbWIeo5j7v52b4YtCU1EO2LbndzLdSzvdmlMf4f3ebpIc9rODNctX5F1n0euM=
X-Received: by 2002:a2e:59ca:: with SMTP id
	g71-v6mr10969809ljf.79.1541993046215; 
	Sun, 11 Nov 2018 19:24:06 -0800 (PST)
MIME-Version: 1.0
References: <CAEPKjgeJX7-LaJNkVk0GKbC5KhOE0aT+otpa-N1EVtwC35m9LQ@mail.gmail.com>
	<prvlaj$8er$1@blaine.gmane.org> <20181108131130.134b2d43@simplexum.com>
	<ps1kj6$fk5$1@blaine.gmane.org> <20181108230004.3f9cabcb@simplexum.com>
In-Reply-To: <20181108230004.3f9cabcb@simplexum.com>
From: Adam Ficsor <adam.ficsor73@gmail.com>
Date: Mon, 12 Nov 2018 10:23:53 +0700
Message-ID: <CAEPKjge8+BsV7Mo2wRtEVWyfF-8LJq4y2tY5qmtVLE41ahcsRg@mail.gmail.com>
To: dp@simplexum.com, bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="000000000000c4125d057a6f3bf8"
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
	HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Mon, 12 Nov 2018 03:41:09 +0000
Cc: andreas@schildbach.de
Subject: Re: [bitcoin-dev] BIP Proposal - Address Paste Improvement
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2018 03:24:09 -0000

--000000000000c4125d057a6f3bf8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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
>


--=20
Best,
=C3=81d=C3=A1m

--000000000000c4125d057a6f3bf8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Thank you for all your comments. To sum u=
p:=C2=A0<br><br>- There were no comments related to the implementation deta=
ils.<br>- There are concerns about this may incentivize users to use copypa=
ste 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 m=
ove to other ways of specifying destinations, that may end up being just as=
 an issue, too.</div><div dir=3D"ltr">- The rest of the conversation was ab=
out crypto hijackers, which I think is off topic in this thread.<br><br>Fin=
ally I&#39;d like to note, there&#39;s already a work in progress implement=
ation in Wasabi:=C2=A0<a href=3D"https://github.com/zkSNACKs/WalletWasabi/p=
ull/825">https://github.com/zkSNACKs/WalletWasabi/pull/825</a></div></div><=
br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Nov 9, 2018 at 1:14 =
AM Dmitry Petukhov via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.=
linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><br>
&gt; &gt; Do you know any reasonably convenient mechanism for end user to<b=
r>
&gt; &gt; transfer an address from, say, a web page to the wallet address<b=
r>
&gt; &gt; input field ?=C2=A0 <br>
&gt; <br>
&gt; - QR code scanning of a Bitcoin URI<br>
&gt; - On Android: A &quot;bitcoin:&quot; URI intent or a BIP70 payment mes=
sage<br>
&gt; intent<br>
&gt; - On desktop OSes there are similar mechanisms to launch Apps from the=
<br>
&gt; 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>
&gt; For cases where the payee is a well-known entity the BIP70 payment<br>
&gt; protocol has authentication via certificates. That doesn&#39;t work fo=
r<br>
&gt; the &quot;the person in front of you is the only trust anchor you have=
&quot;<br>
&gt; 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=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"l=
tr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div><span style=3D"fo=
nt-size:13.3333339691162px">Best,<br>=C3=81d=C3=A1m</span></div></div></div=
></div></div></div></div></div>

--000000000000c4125d057a6f3bf8--