path: root/3f/741559c040010002ed325a6d135b2d95a3f329

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 F3ABE74
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat,  1 Dec 2018 12:07:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com
	[209.85.208.179])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EB2B627B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat,  1 Dec 2018 12:07:54 +0000 (UTC)
Received: by mail-lj1-f179.google.com with SMTP id c19-v6so7328094lja.5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 01 Dec 2018 04:07:54 -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=M+oGx3UJXb+b1WjYS6G2N1FQET6zdAFlBeXRnR4xfV4=;
	b=ibhsEUFp8zXEKTaS1Vk/dhbgqAVsirLHy77ynihNY5zS4M7Xllrl9k9hemFFvgx85L
	12QEgXN6cKlkwpXUoZZV5a2uslDOFdHT9C7g/mp8EsJ91FHDD9AorZSyjbGQaODzQ7YF
	zqHx3pMhFjQYqevkPJUuy35Y4utZabM0byCxtumJFNBy4SIvBCHidOybL054SbM3PhPY
	36T0SaS1NC2n8tAsgFO3lt/219eUwL22d1sRhxsHR6wDClwHbHnjRYQ+ILIv0ET/cbhw
	lrhGyLI833hevwV+yOXLc62Zd10PzwZbPGHY3BnBc+XnWzTwoSY8JsnGvVsF6NwYhbt3
	qcDQ==
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=M+oGx3UJXb+b1WjYS6G2N1FQET6zdAFlBeXRnR4xfV4=;
	b=evrFFHIltwn/kfuE4mbPNXi0kFCM21yzCViqOP4a79C4H+EE3aPpISugwksNkAmsuq
	FCfrHvcEHfIVhwiiwyzUrlwOMK6iFXl2pGRRCDkXnlGWuZ9W0WO35xpJskXHblyaMWXw
	lzBokz9E3VzvsXp0K+Gf/LwntJzY04P4d/4J/yOSA4FSwvGG/KZiInmmZV7JLeCOcPl5
	B1WphnjR9bSoiYjvo72Gxztd9W3zkkqnldip5SZiqNXot/FTUfuyzImG21e1/X1l+KDa
	uDo2+/j9nQ1hE5TtXdI7xW72s1JbM5G0i/6LLwY3bwQDD1n6Ps3DIG2GKVd4nLQOI9YP
	MNZg==
X-Gm-Message-State: AA+aEWb9DN7Xw20BmmOsSiRT8HAYpZvILbI46aAJfaSkVx4JH+Ux3zNE
	vpCXFaYKg5/Ct/nl8ceubn+BkN+X/YdrX4FbWLM=
X-Google-Smtp-Source: AFSGD/UqBI0/CB9alByC+mb2QXFXRG79gPbtbE1jwA+rvcUPGqVCSQE75V9G+sAj9a+/+6RAe4M9QywK7totTboocls=
X-Received: by 2002:a2e:2019:: with SMTP id
	g25-v6mr5697933ljg.20.1543666073106; 
	Sat, 01 Dec 2018 04:07:53 -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>
	<CAEPKjge8+BsV7Mo2wRtEVWyfF-8LJq4y2tY5qmtVLE41ahcsRg@mail.gmail.com>
	<CAH+Axy4dwjKebmZfz8+-MW4ghNnhiDCe7_rFcXBE7pK+5enJzw@mail.gmail.com>
In-Reply-To: <CAH+Axy4dwjKebmZfz8+-MW4ghNnhiDCe7_rFcXBE7pK+5enJzw@mail.gmail.com>
From: Adam Ficsor <adam.ficsor73@gmail.com>
Date: Sat, 1 Dec 2018 19:07:40 +0700
Message-ID: <CAEPKjgfUox5Cw6ZLdQHBXZX64MGFJqAKRneydLRj7PxcCfGB8w@mail.gmail.com>
To: macwhyte@gmail.com
Content-Type: multipart/alternative; boundary="000000000000f0885b057bf4c3d9"
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: Sat, 01 Dec 2018 14:03:59 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org, 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: Sat, 01 Dec 2018 12:07:56 -0000

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

If this needs to be a BIP or not, that is up to this list to decide, I will
not be pushy abut it. We simply encountered a well defined and common issue
and we took the time to work out and specify our solution, so it may come
in handy for other developers encountering this same issue. We can argue
about the significance of it, but I suspect all arguments will come down to
how much an individual developer values UX or how much he does not.

On Sat, Dec 1, 2018 at 11:57 AM James MacWhyte <macwhyte@gmail.com> wrote:

> 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 ca=
n
>> 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 th=
e
>>> > 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,
>> =C3=81d=C3=A1m
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>

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

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

<div dir=3D"ltr">If this needs to be a BIP or not, that is up to this list =
to decide, I will not be pushy abut it. We simply encountered a well define=
d and common issue and we took the time to work out and specify our solutio=
n, so it may come in handy for other developers encountering this same issu=
e. We can argue about the significance of it, but I suspect all arguments w=
ill come down to how much an individual developer values UX or how much he =
does not.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sat, Dec =
1, 2018 at 11:57 AM James MacWhyte &lt;<a href=3D"mailto:macwhyte@gmail.com=
">macwhyte@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div dir=3D"ltr">I liked the cheekiness of your summary, Adam ;)<div><br><=
/div><div>I&#39;m not sure why this needs to be a BIP. It is a UX detail--n=
ot really related to bitcoin protocol or procedures. I wouldn&#39;t even ca=
ll it a description of best practices, since every product&#39;s use case i=
s going to be different.</div><div><br></div><div>If you think there is a c=
ompelling reason for why this needs to be a documented standard, please ela=
borate!</div><div><br></div><div>Thanks,</div><div><div><div dir=3D"ltr" cl=
ass=3D"m_7504265157336305511gmail_signature" data-smartmail=3D"gmail_signat=
ure"><div dir=3D"ltr"><div>James<br></div></div></div></div><br></div></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sun, Nov 11, 2018 at 7:=
41 PM Adam Ficsor via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.l=
inuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><d=
iv dir=3D"ltr">Thank you for all your comments. To sum up:=C2=A0<br><br>- T=
here were no comments related to the implementation details.<br>- There are=
 concerns about this may incentivize users to use copypaste functionality e=
xtensively.<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 o=
f specifying destinations, that may end up being just as an issue, too.</di=
v><div dir=3D"ltr">- The rest of the conversation was about crypto hijacker=
s, which I think is off topic in this thread.<br><br>Finally I&#39;d like t=
o note, there&#39;s already a work in progress implementation in Wasabi:=C2=
=A0<a href=3D"https://github.com/zkSNACKs/WalletWasabi/pull/825" target=3D"=
_blank">https://github.com/zkSNACKs/WalletWasabi/pull/825</a></div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Nov 9, 2018 at 1:14 A=
M Dmitry Petukhov via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.l=
inuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org=
</a>&gt; wrote:<br></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"m_7504265157336305511m_-8626222342460661196gmail_signature" data-=
smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><=
div dir=3D"ltr"><div><div><span style=3D"font-size:13.3333339691162px">Best=
,<br>=C3=81d=C3=A1m</span></div></div></div></div></div></div></div></div>
_______________________________________________<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>
</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>

--000000000000f0885b057bf4c3d9--