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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WW4Tm-0005sj-GU
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 13:48:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.160.170 as permitted sender)
client-ip=209.85.160.170; envelope-from=jgarzik@bitpay.com;
helo=mail-yk0-f170.google.com;
Received: from mail-yk0-f170.google.com ([209.85.160.170])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WW4Tl-0002yJ-PI
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 13:48:22 +0000
Received: by mail-yk0-f170.google.com with SMTP id 9so2928198ykp.29
for <bitcoin-development@lists.sourceforge.net>;
Fri, 04 Apr 2014 06:48:16 -0700 (PDT)
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:from:date
:message-id:subject:to:cc:content-type;
bh=soXvZvOGu+YksLUZ0yi/cb5R+zHTpRwYXBJag9Yi6C8=;
b=MuewcXU5wIgOirKaHB9yo4EX9lR7PIrku5AFS/6WuaLuTYGInjjLUdatBcZ597nL/G
uzsb+YtU7EEEwHjjz9UDpoQIF5Hrdm6BA955jYpWZfgGUbyg93K8NxwYDnrZpuSx/I7t
OdF3YKiXpFjSpYC8B/zwgYQuF16g/SGZKxEWJitUCcj+mlsOcaVvRQGl4jcONZn0hkHF
tXn7qNmHaQlqieoShpHRDKSys0nTajvDnvlWOANG59CozvabzyPVzBX3+KpwpohXHKU2
BvkO4sEf37US3rJc5+raa8v+Dv7exd5bYXEE+a/eU2eyQXP6CnX5XXGYjgXwMCGo9dI6
fheg==
X-Gm-Message-State: ALoCoQkj2kvcVwp2WDZpWeGOTxuBYwOkb5mOEUwyXEt9S5WZrKJYSKUQaPTjpGvrnHxKHmpBE64N
X-Received: by 10.236.156.65 with SMTP id l41mr17274458yhk.9.1396619296234;
Fri, 04 Apr 2014 06:48:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.170.162.214 with HTTP; Fri, 4 Apr 2014 06:47:56 -0700 (PDT)
In-Reply-To: <CANEZrP0DTYqobECBbw6eZqdk+-TR_2jhBtOviN08r31EQGmZHQ@mail.gmail.com>
References: <CA+WZAEp3HsW5ESGUZ7YfR1MZXGC5jd+LucUt_MUP8K94Xwhuhg@mail.gmail.com>
<CANEZrP0KVyp2Va7Wyy=t0qYkLNK9BDUaSzBfuzQss+=weLJ1Fw@mail.gmail.com>
<CA+WZAEqYKv8T1OMCKhOJvf5FAy=WujJ=OhtsYP9aBf=4ZPNxmw@mail.gmail.com>
<CANEZrP0DTYqobECBbw6eZqdk+-TR_2jhBtOviN08r31EQGmZHQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 4 Apr 2014 09:47:56 -0400
Message-ID: <CAJHLa0PeD6Fkc1N=JSqmC0cNjPNxZ8p5qCMr1+E--JUeUFdhZQ@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
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: 1WW4Tl-0002yJ-PI
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Draft BIP for seamless website
authentication using Bitcoin address
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: Fri, 04 Apr 2014 13:48:22 -0000
On Fri, Apr 4, 2014 at 9:43 AM, Mike Hearn <mike@plan99.net> wrote:
> These are the kinds of problems that crop up when you mix together two
> different things: the act of paying, and the act of identifying yourself.
This is precisely why SINs use a different version byte from bitcoin
addresses. There should never be any confusion between money/payments
and identity.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
