From: Dmitry Petukhov <dp@simplexum•com>
To: bitcoin-dev@lists•linuxfoundation.org
Cc: Andreas Schildbach <andreas@schildbach•de>
Subject: Re: [bitcoin-dev] BIP Proposal - Address Paste Improvement
Date: Thu, 8 Nov 2018 23:00:04 +0500 [thread overview]
Message-ID: <20181108230004.3f9cabcb@simplexum.com> (raw)
In-Reply-To: <ps1kj6$fk5$1@blaine.gmane.org>
> > 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).
next prev parent reply other threads:[~2018-11-08 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 14:09 Adam Ficsor
2018-11-07 21:28 ` Andreas Schildbach
2018-11-08 8:11 ` Dmitry Petukhov
2018-11-08 15:28 ` Andreas Schildbach
2018-11-08 18:00 ` Dmitry Petukhov [this message]
2018-11-12 3:23 ` Adam Ficsor
2018-12-01 4:57 ` James MacWhyte
2018-12-01 12:07 ` Adam Ficsor
2018-11-08 17:43 ` Moral Agent
2018-11-08 17:12 ` Jeffrey Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181108230004.3f9cabcb@simplexum.com \
--to=dp@simplexum$(echo .)com \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox