From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VIQJE-0000SA-3U for bitcoin-development@lists.sourceforge.net; Sat, 07 Sep 2013 21:44:48 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.42 as permitted sender) client-ip=209.85.219.42; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f42.google.com; Received: from mail-oa0-f42.google.com ([209.85.219.42]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VIQJA-0005mL-7l for bitcoin-development@lists.sourceforge.net; Sat, 07 Sep 2013 21:44:48 +0000 Received: by mail-oa0-f42.google.com with SMTP id n12so5373215oag.15 for ; Sat, 07 Sep 2013 14:44:38 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.51.196 with SMTP id m4mr6673235obo.28.1378590278304; Sat, 07 Sep 2013 14:44:38 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.80.165 with HTTP; Sat, 7 Sep 2013 14:44:38 -0700 (PDT) In-Reply-To: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com> References: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com> Date: Sat, 7 Sep 2013 23:44:38 +0200 X-Google-Sender-Auth: 34Kei6wrIUwH0L4mS-QCi17-oZE Message-ID: From: Mike Hearn To: Wendell Content-Type: multipart/alternative; boundary=089e0111d5ead44a8a04e5d20f05 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VIQJA-0005mL-7l Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Simple contacts exchange (was: Social network integration (brainstorm)) X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Sep 2013 21:44:48 -0000 --089e0111d5ead44a8a04e5d20f05 Content-Type: text/plain; charset=UTF-8 This is the sort of thing the payment protocol is for. The recipient would vend a PaymentRequest containing identity details. The sender would submit a Payment containing his/hers. The wallet then understands what to do. On Fri, Sep 6, 2013 at 5:07 PM, Wendell wrote: > Hi all, > > We're thinking about ways of automatically exchanging contact details > between wallets, in order to encourage the proliferation of identifiable > names and photos rather than long and hard-to-verify addresses. > > The simplest version goes like this: > > 2 BTC Bitcoin is sent to someone, and a data lookup hash is inserted into > the transaction. When it arrives on the other end, it is indeed looked up, > and instead of being presented with a dialogue that says "you received 2 > BTC from 13Y94z43Nbbb6wevRyk82CeDoYQ5S28zmA", it's "You received 2 BTC from > Frank Jones" including a nice photo. > > Now. We can simply delete this data in reference to the transaction ID > after it happens (or delete it after a time), but is there any more > decentralized way to do it? I would prefer us to run no dedicated servers > that would ever put us in a position of being coerced into giving data, or > otherwise altering our system to store it. > > Any thoughts about this? > > -wendell > > grabhive.com | twitter.com/grabhive | gpg: 6C0C9411 > > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --089e0111d5ead44a8a04e5d20f05 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This is the sort of thing the payment protocol is for. The= recipient would vend a PaymentRequest containing identity details. The sen= der would submit a Payment containing his/hers. The wallet then understands= what to do.


On Fri, Sep 6= , 2013 at 5:07 PM, Wendell <w@grabhive.com> wrote:
Hi all,

We're thinking about ways of automatically exchanging contact details b= etween wallets, in order to encourage the proliferation of identifiable nam= es and photos rather than long and hard-to-verify addresses.

The simplest version goes like this:

2 BTC Bitcoin is sent to someone, and a data lookup hash is inserted into t= he transaction. When it arrives on the other end, it is indeed looked up, a= nd instead of being presented with a dialogue that says "you received = 2 BTC from 13Y94z43Nbbb6wevRyk82CeDoYQ5S28zmA", it's "You rec= eived 2 BTC from Frank Jones" including a nice photo.

Now. We can simply delete this data in reference to the transaction ID afte= r it happens (or delete it after a time), but is there any more decentraliz= ed way to do it? I would prefer us to run no dedicated servers that would e= ver put us in a position of being coerced into giving data, or otherwise al= tering our system to store it.

Any thoughts about this?

-wendell

grabhive.com | twitter.com/grabhive | gpg: 6C0C9411


-----------------------------------------------------------------------= -------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies=
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D58041391&iu=3D/4140/ostg.clktrk
___________________= ____________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--089e0111d5ead44a8a04e5d20f05--