diff options
| author | James MacWhyte <macwhyte@gmail.com> | 2018-11-30 20:57:20 -0800 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2018-12-01 04:57:50 +0000 |
| commit | df1423ee0ffa8c9d1ba5ab7c4a290fac6f21d89f (patch) | |
| tree | 80272624071032ae79ccb57dc3b35938362967d6 | |
| parent | 94bddc2556b7b56cfa9b0fdd5712628f6fb4c7eb (diff) | |
| download | pi-bitcoindev-df1423ee0ffa8c9d1ba5ab7c4a290fac6f21d89f.tar.gz pi-bitcoindev-df1423ee0ffa8c9d1ba5ab7c4a290fac6f21d89f.zip | |
Re: [bitcoin-dev] BIP Proposal - Address Paste Improvement
| -rw-r--r-- | 65/f96ee3c5b4cce5c323759c5d92ef06f08717d4 | 248 |
1 files changed, 248 insertions, 0 deletions
diff --git a/65/f96ee3c5b4cce5c323759c5d92ef06f08717d4 b/65/f96ee3c5b4cce5c323759c5d92ef06f08717d4 new file mode 100644 index 000000000..56f7c6ea1 --- /dev/null +++ b/65/f96ee3c5b4cce5c323759c5d92ef06f08717d4 @@ -0,0 +1,248 @@ +Return-Path: <keatonatron@gmail.com> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id 079C1504 + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 1 Dec 2018 04:57:50 +0000 (UTC) +X-Greylist: whitelisted by SQLgrey-1.7.6 +Received: from mail-wr1-f52.google.com (mail-wr1-f52.google.com + [209.85.221.52]) + by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 07115827 + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 1 Dec 2018 04:57:48 +0000 (UTC) +Received: by mail-wr1-f52.google.com with SMTP id v6so7091382wrr.12 + for <bitcoin-dev@lists.linuxfoundation.org>; + Fri, 30 Nov 2018 20:57:48 -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=FuTyzTrm/GKpiWNnAxL24sisceycVgQeN+/jPCPf8/o=; + b=XbSmvYSFBWXoEvcK0+okBNo7cApsue9LUowo5pyn6JjqkQpMtjARtKSPJJJ1n9pq0B + 6yZ2vEZ9Tz8SSR5MPenayEjhDHRfxLM8IOs84VuuP1EVmvytSl33fZZdKApiXbp4RfFV + i0y3EcPbMOtiGCNI2kFTAazOUSyH4l7ryuYQCfRx+SV7e06Qxa0NebrmXR4HQp8I0MY5 + 3PFOK4atEX1MtLsJmVomYUuxTou0ul5hE4AFaIKU2Lv3+WXqQZehbadV1a+jFmtnZRnA + 9iJ6ogZkymesiYik66Z5+4YeUTAkvLmDHgg9kpKFRBvrEDHIxGIwajC/RD+tsG6Pw6FJ + L/7Q== +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=FuTyzTrm/GKpiWNnAxL24sisceycVgQeN+/jPCPf8/o=; + b=GftR3sQWR07rY27nu7fAL/ROnIFJCMkBFWMezKiqWlu4vPWmwqMa52ZdQf9cBUgZwr + dlB4XWQSodEnr3X+igdLNN9vj5+2ua+lW+4w3t0c07Wy/fhSZAeSQImUrRBNf1BL50/1 + 1KuQSXyIsofEy/zxV6vAr3JIVBahPFn/H+dit7zCfFKD4HQlsRXNXlFAlcRtMZJ1IFH4 + UAM5ID469FOAsr7bEpxiY3TTbsH5ZmpAypy9I/W+9pCPBGx7ka7DatL58rIO7fMIKcXV + TnxH7Tcq2BDRmwVrMCNyoUeO8BZxXrmb2BGKsMoZUELuIGqStC+SuOt01Bpyo5TZPvW6 + tiNw== +X-Gm-Message-State: AA+aEWaN1I2r8/UeapqkxvzseupQaDBBKa28yWRa2cpbTIODa3s80ORF + fUlEo4BOzLhA55do3BZFW7O1NwO9ua/hePOVCXU= +X-Google-Smtp-Source: AFSGD/WAI3p3mF6j8lCL+oxrlrQ3oU06FcFZeQDu1ROQfxXNjvn36HxML+dKvBvbAklhlJzfnYj3A0lgPSSnECPdaNo= +X-Received: by 2002:adf:e707:: with SMTP id c7mr6718062wrm.196.1543640267402; + Fri, 30 Nov 2018 20:57:47 -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> +In-Reply-To: <CAEPKjge8+BsV7Mo2wRtEVWyfF-8LJq4y2tY5qmtVLE41ahcsRg@mail.gmail.com> +From: James MacWhyte <macwhyte@gmail.com> +Date: Fri, 30 Nov 2018 20:57:20 -0800 +Message-ID: <CAH+Axy4dwjKebmZfz8+-MW4ghNnhiDCe7_rFcXBE7pK+5enJzw@mail.gmail.com> +To: adam.ficsor73@gmail.com, + Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> +Content-Type: multipart/alternative; boundary="000000000000ccb331057beec132" +X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, + DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, + RCVD_IN_DNSWL_NONE autolearn=ham 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:04:10 +0000 +Cc: Andreas Schildbach <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 04:57:50 -0000 + +--000000000000ccb331057beec132 +Content-Type: text/plain; charset="UTF-8" +Content-Transfer-Encoding: quoted-printable + +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, +> =C3=81d=C3=A1m +> _______________________________________________ +> bitcoin-dev mailing list +> bitcoin-dev@lists.linuxfoundation.org +> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev +> + +--000000000000ccb331057beec132 +Content-Type: text/html; charset="UTF-8" +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr">I liked the cheekiness of your summary, Adam ;)<div><br></= +div><div>I'm not sure why this needs to be a BIP. It is a UX detail--no= +t really related to bitcoin protocol or procedures. I wouldn't even cal= +l it a description of best practices, since every product's use case is= + going to be different.</div><div><br></div><div>If you think there is a co= +mpelling reason for why this needs to be a documented standard, please elab= +orate!</div><div><br></div><div>Thanks,</div><div><div><div dir=3D"ltr" cla= +ss=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">= +<div>James<br></div></div></div></div><br></div></div><br><div class=3D"gma= +il_quote"><div dir=3D"ltr">On Sun, Nov 11, 2018 at 7:41 PM Adam Ficsor via = +bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bi= +tcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div><blockquote cla= +ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa= +dding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">Thank you for all your co= +mments. To sum up:=C2=A0<br><br>- There were no comments related to the imp= +lementation details.<br>- There are concerns about this may incentivize use= +rs to use copypaste functionality extensively.<br>- A counter argument was = +made that crypto hijackers use the clipboard, because that is the most conv= +enient thing to hijack, not because they can only hijack that and, if Bitco= +in users would move 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 con= +versation was about crypto hijackers, which I think is off topic in this th= +read.<br><br>Finally I'd like to note, there's already a work in pr= +ogress implementation in Wasabi:=C2=A0<a href=3D"https://github.com/zkSNACK= +s/WalletWasabi/pull/825" target=3D"_blank">https://github.com/zkSNACKs/Wall= +etWasabi/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 <<a= + href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bi= +tcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div><blockquote cla= +ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa= +dding-left:1ex"><br> +> > Do you know any reasonably convenient mechanism for end user to<b= +r> +> > transfer an address from, say, a web page to the wallet address<b= +r> +> > input field ?=C2=A0 <br> +> <br> +> - QR code scanning of a Bitcoin URI<br> +> - On Android: A "bitcoin:" URI intent or a BIP70 payment mes= +sage<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 fo= +r<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=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_-8626222342460661196gmail_signature" data-smartmail=3D"gmail_si= +gnature"><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> + +--000000000000ccb331057beec132-- + |