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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <eric@voskuil.org>) id 1YQ35U-00016w-PC
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Feb 2015 00:10:57 +0000
X-ACL-Warn:
Received: from mail-pa0-f45.google.com ([209.85.220.45])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YQ35T-0007nD-TV
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Feb 2015 00:10:56 +0000
Received: by pablf10 with SMTP id lf10so31450436pab.6
for <bitcoin-development@lists.sourceforge.net>;
Mon, 23 Feb 2015 16:10:50 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
:cc:subject:references:in-reply-to:content-type;
bh=hYNsJSmMmGfFqXs4OIbjSFQvE9xvhNV31kWvzHv8X28=;
b=hKJE9wbdASEfFyFA9u8UzkJXe5cJeH5bMF2CcrmkRTdDxhER9R/NaA4CHwKFLbNyxp
8uDgzXH147gTvQk4apfVSxGhj7ITTJl+a/nBRQH0yTWA9QRddw6HlvLkluAEMnIaCE4n
ljeuUzEntY0n+m+aQlqKzN7MhdMepYNWT9FRjBgQs53+tTHxjEvDiuHLYJY/Cs7UyB//
EBc+8F4u6F+Bfz8Ebb06857vG0+8sNazt48pEJ1julTTotYjrbyvoJi6eVi1WAEOolP2
kbe0q1022FN1EAmQwwjqT0hilK5mR9PLfRlTwV6YdIEeezvGm10HsYEjjV26NfiDcfm+
YNmQ==
X-Gm-Message-State: ALoCoQl9yA/g0i+9dVX1ar9eAeJeUwKpwTvUJk504xexiVk0djHNY1ZB7/YGNZie9WDqnYZtmQVl
X-Received: by 10.70.126.167 with SMTP id mz7mr23455097pdb.109.1424736650142;
Mon, 23 Feb 2015 16:10:50 -0800 (PST)
Received: from [10.0.1.3] (c-50-135-46-157.hsd1.wa.comcast.net.
[50.135.46.157])
by mx.google.com with ESMTPSA id kn4sm3811222pab.48.2015.02.23.16.10.48
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Mon, 23 Feb 2015 16:10:49 -0800 (PST)
Message-ID: <54EBC187.2050600@voskuil.org>
Date: Mon, 23 Feb 2015 16:10:47 -0800
From: Eric Voskuil <eric@voskuil.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Mike Hearn <mike@plan99.net>
References: <20150222190839.GA18527@odo.localdomain> <54EA5A1C.2020701@AndySchroder.com> <54EA60D9.8000001@voskuil.org> <54EA66F5.2000302@AndySchroder.com> <mcdu6b$j11$1@ger.gmane.org> <54EAD884.8000205@AndySchroder.com> <mcet2t$qav$1@ger.gmane.org> <54EAFC1C.9080502@voskuil.org> <CANEZrP0XYfnarvN5H_NeOGyO8RLBSGyGxv7M63MSrAd_HXj1OQ@mail.gmail.com> <54EBB10D.8020502@voskuil.org>
<CANEZrP1F4tGOQuF6b9JV6_n0YmrzmerPp1WMzQor8BggkgAB5Q@mail.gmail.com>
In-Reply-To: <CANEZrP1F4tGOQuF6b9JV6_n0YmrzmerPp1WMzQor8BggkgAB5Q@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="FFC3aA7CfqoRD34tJBXIIE41lWu3Q72dK"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1YQ35T-0007nD-TV
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] Bitcoin at POS using BIP70,
NFC and offline payments - implementer feedback
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: Tue, 24 Feb 2015 00:10:58 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--FFC3aA7CfqoRD34tJBXIIE41lWu3Q72dK
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
On 02/23/2015 03:11 PM, Mike Hearn wrote:
>> I don't see how you propose to treat the bitcoin address as a
>> secp256k1 public key, or do you mean something else?
>
> Sorry, I skipped a step. I shouldn't make assumptions about what's
> obvious.
No problem, we don't all have the same context. I may have missed prior
discussion.
> The server would provide the public key and the client would
> convert it to address form then match against the URI it has scanned.
> If it didn't match, stop at that point.
Does this not also require the BT publication of the script for a P2SH
address?
e
--FFC3aA7CfqoRD34tJBXIIE41lWu3Q72dK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJU68GHAAoJEDzYwH8LXOFObBMH/0SPjHjk96h2W9BLrlC5eZ6k
We8KP6N7azQRvkDiizmKfbCsYcvSYcC++OxE23a4394Iv+Qc6EaM078E+qPR/3/3
O+L7cHryNPcxgiAmMC8lEnve8EwQnmkp3E8eB9kgtRFj81d3xyj7uLTbgmtZZCWc
zdZs5kx3aJaGA2/jFaD8wMsyTPdKa9swImhP9EiB/Sc9mZpIS2vQeAUSGaBM3ZHB
c8VrIs6PsP1kHUou4xt/AbjGdBH0sG2e0d4+7ry2zRFyc/67aSBaAhHwMhgkn14J
qW7BQGJtuGqezIvaepD7M2D22A+z8R991FSAy/bWs8ywG41NbGVnjjGedhZ7C1w=
=S6Xe
-----END PGP SIGNATURE-----
--FFC3aA7CfqoRD34tJBXIIE41lWu3Q72dK--
|
