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
114
115
116
117
118
119
120
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1XBl2z-00082B-U4
for bitcoin-development@lists.sourceforge.net;
Mon, 28 Jul 2014 13:33:02 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.46 as permitted sender)
client-ip=209.85.219.46; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f46.google.com;
Received: from mail-oa0-f46.google.com ([209.85.219.46])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XBl2y-0004zl-9G
for bitcoin-development@lists.sourceforge.net;
Mon, 28 Jul 2014 13:33:01 +0000
Received: by mail-oa0-f46.google.com with SMTP id m1so8632158oag.5
for <bitcoin-development@lists.sourceforge.net>;
Mon, 28 Jul 2014 06:32:54 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.158.8 with SMTP id wq8mr21966701oeb.40.1406554374724;
Mon, 28 Jul 2014 06:32:54 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Mon, 28 Jul 2014 06:32:54 -0700 (PDT)
In-Reply-To: <5E988ED7-845D-4982-9240-155AACD20F66@coinqy.com>
References: <B097D5C5-8E9E-461D-8FF3-58A661AFB3CB@coinqy.com>
<CANEZrP0u-yoS4Sx2sC9uCf0xnzm-g1gYP8atUQO9-s3PW2kYKw@mail.gmail.com>
<C9BF4A1A-5363-4725-8CFC-9EFE0C0B6B15@coinqy.com>
<CANEZrP3pU__65h3VFEshtHuXE-aXWkRR47QPXXMNmBrBNcb=SQ@mail.gmail.com>
<5E988ED7-845D-4982-9240-155AACD20F66@coinqy.com>
Date: Mon, 28 Jul 2014 15:32:54 +0200
X-Google-Sender-Auth: A8VgjxyKTMvoq6Ouz59bkPwBX4c
Message-ID: <CANEZrP1tn_j-bjcbokq-egVhS_x7M-L06bLb8toJeTg6oT+mcg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Mark van Cuijk <mark@coinqy.com>
Content-Type: multipart/alternative; boundary=047d7bd6ac48dce87f04ff40f595
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: 1XBl2y-0004zl-9G
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] "On behalf of" BIP 70 extension proposal
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: Mon, 28 Jul 2014 13:33:02 -0000
--047d7bd6ac48dce87f04ff40f595
Content-Type: text/plain; charset=UTF-8
>
> I referred to your idea in
> https://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg04076.html
> <https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg04076.html> which
> is indeed not the proposal itself.
>
Right, gotcha. Had forgotten about that.
Indeed there is another signature, which is to authenticate the payment
> delegation. If you take it into account in the signature count, then your
> proposal has three signatures.
>
Yes, I see now, you are right. A mandate type system is probably simpler
indeed.
So what now? To be honest my next priority with BIP70 was to formalise the
extensions process, I've been dragging my feet over that because I'm
working on other things. And then after that to knock some heads together
over at BitPay/Coinbase and get them to put useful text in the memo field
instead of random numbers. Baby steps ....
--047d7bd6ac48dce87f04ff40f595
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>I refer=
red to your idea in=C2=A0<a href=3D"https://www.mail-archive.com/bitcoin-de=
velopment@lists.sourceforge.net/msg04076.html" target=3D"_blank">https://ww=
w.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg04076.htm=
l</a>=C2=A0which is indeed not the proposal itself.</div>
</div></blockquote><div><br></div><div>Right, gotcha. Had forgotten about t=
hat.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-=
wrap:break-word">
<div class=3D""><div>Indeed there is another signature, which is to authent=
icate the payment delegation. If you take it into account in the signature =
count, then your proposal has three signatures.<br></div></div></div></bloc=
kquote>
<div><br></div><div>Yes, I see now, you are right. A mandate type system is=
probably simpler indeed.</div><div><br></div><div>So what now? To be hones=
t my next priority with BIP70 was to formalise the extensions process, I=
9;ve been dragging my feet over that because I'm working on other thing=
s. And then after that to knock some heads together over at BitPay/Coinbase=
and get them to put useful text in the memo field instead of random number=
s. Baby steps ....</div>
</div></div></div>
--047d7bd6ac48dce87f04ff40f595--
|
