From: Mike Hearn <mike@plan99•net>
To: Taylor Gerring <taylor.gerring@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Extending the Payment Protocol with vCards
Date: Sun, 10 Nov 2013 12:08:38 +0100 [thread overview]
Message-ID: <CANEZrP0tAb0G700qXhmWJ4ChEfys87KCwUp1CAUQ9sfyHOCxbQ@mail.gmail.com> (raw)
In-Reply-To: <0887034B-AA65-468B-A8DB-4DF1E6C27DA2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2997 bytes --]
Hey Taylor,
It's great to see people thinking about payment protocol extensions. I'm
not totally convinced vCard support is the best idea relative to social
network integration - I can't recall the last time I saw someone use a
vCard. However, that should not hold you back from experimenting or
prototyping. All an extension requires is some tag numbers and we're not in
danger of running out of numbers any time soon.
The reason I favour social network integration is because those are the
ID's people already have. Distributed social networks (like the PGP web of
trust) have never really taken off, and fixing that is an entirely separate
project to Bitcoin.
Doing so is quite easy. Major social networks all have a concept of a user
ID, moreover, one that can be queried without any kind of API authorization
for basic info. Examples:
https://graph.facebook.com/i.am.the.real.mike
https://plus.google.com/s2/u/0/photos/profile/114798402540078632611
So you could simply embed a social network URL into a payment request, and
use that to associate a name/photo with a payment. That would be
unauthenticated (the sender is not proving they are the real owner of the
social network profile). However, authentication may not turn out to be
necessary. If it were to be, then steganographically embedding a key into
the profile picture and signing the payment request with it would be a way
to do so.
On Sat, Nov 9, 2013 at 6:43 PM, Taylor Gerring <taylor.gerring@gmail•com>wrote:
> Hi everyone,
>
> I made a post on the BitcoinTalk forums <
> https://bitcointalk.org/index.php?topic=329229.0> outlining how the
> Payment Protocol could be extended with optional vCard support to increase
> the usability of Payment Protocol for user-to-user transactions and improve
> the user experience in wallets supporting PP.
>
> I’ve outlined the concept in as much detail as my feeble brain can handle,
> drawing on BIP 0070 itself and Mike Hearn’s Payment Protocol FAQ. I know
> there is interest in “contact exchange” functionality from the Hive team,
> so I’m hoping this will begin a discussion on how we can make wallets more
> friendly in a standard way.
>
> Please read, digest, and let me know if you have any feedback.
>
> Thanks,
>
> Taylor Gerring
>
>
>
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models.
> Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and
> register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 3958 bytes --]
next prev parent reply other threads:[~2013-11-10 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 17:43 Taylor Gerring
2013-11-10 11:08 ` Mike Hearn [this message]
2013-11-12 18:34 ` Wendell
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=CANEZrP0tAb0G700qXhmWJ4ChEfys87KCwUp1CAUQ9sfyHOCxbQ@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=taylor.gerring@gmail$(echo .)com \
/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