1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WG7rW-000767-0j
for bitcoin-development@lists.sourceforge.net;
Wed, 19 Feb 2014 14:10:58 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.169 as permitted sender)
client-ip=74.125.82.169; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f169.google.com;
Received: from mail-we0-f169.google.com ([74.125.82.169])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WG7rT-0000bc-Ai
for bitcoin-development@lists.sourceforge.net;
Wed, 19 Feb 2014 14:10:57 +0000
Received: by mail-we0-f169.google.com with SMTP id t61so375456wes.28
for <bitcoin-development@lists.sourceforge.net>;
Wed, 19 Feb 2014 06:10:49 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=qeI26SREFkuIOau6W/xpfcAhxRVApbrQAsKL+/DPJNQ=;
b=Tkb09YYMiQSoEA5ymN7I4Y27kedrmklznVQ1+6YPEFn8qi7ujxHlE/5uHTuCh20S8E
DV7kK07xH0grUqmGQWa0twO/bmKXvrY9C3rj+KDq41Ft2PdiCFv1s1JW4YZG5So2lc73
u7BMaGhymcXqMOJVIDwh7GKd1ZwauEHz5z6ZcLG7qoMTP4F6Cse2xVS5eTh8ZLJJUVKk
TgX8XJiPnIROVb5gIffpzBKskCZQslP4twTbobpe0XthRcrFaq7B5vMwRQLJBD9U1e9N
tOoQpeWk3jRzwn4rACyfoVD1sLIQXrz5h0mUQBuqp5ZsEvTUYi1UbGMfTzrc4su8mHL2
F2Aw==
X-Gm-Message-State: ALoCoQnZXVvQk3q8q1dqy1j8zwF0w14akF9Fn4J9uCZLb71+GkJTPCu07/hu3qwfPwX+dq1rv0Ed
MIME-Version: 1.0
X-Received: by 10.180.87.162 with SMTP id az2mr1658174wib.23.1392819049187;
Wed, 19 Feb 2014 06:10:49 -0800 (PST)
Received: by 10.194.82.197 with HTTP; Wed, 19 Feb 2014 06:10:49 -0800 (PST)
In-Reply-To: <le0jvf$i7d$1@ger.gmane.org>
References: <le05ca$qn5$1@ger.gmane.org> <5303B110.70603@bitpay.com>
<le0jvf$i7d$1@ger.gmane.org>
Date: Wed, 19 Feb 2014 09:10:49 -0500
Message-ID: <CAJHLa0MGaxJTGPR-bduW36-4Msb348FANqFmw67jqFxq1CLwbw@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
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 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1WG7rT-0000bc-Ai
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70 proposed changes
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 14:10:58 -0000
On Tue, Feb 18, 2014 at 4:40 PM, Andreas Schildbach
<andreas@schildbach.de> wrote:
> On 02/18/2014 08:14 PM, Ryan X. Charles wrote:
>> BitPay is working on a new standard
>> based on bitcoin-like addresses for authentication. It would be great if
>> we could work with the community to establish a complete, decentralized
>> authentication protocol.
>
> Sounds interesting, let us know as soon as you have anything.
SINs. See https://en.bitcoin.it/wiki/Identity_protocol_v1
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
