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
121
122
123
124
125
126
127
128
129
130
131
132
133
|
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 1XCS9y-00073H-Og
for bitcoin-development@lists.sourceforge.net;
Wed, 30 Jul 2014 11:35:06 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.218.48 as permitted sender)
client-ip=209.85.218.48; envelope-from=mh.in.england@gmail.com;
helo=mail-oi0-f48.google.com;
Received: from mail-oi0-f48.google.com ([209.85.218.48])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XCS9x-0008GD-Rq
for bitcoin-development@lists.sourceforge.net;
Wed, 30 Jul 2014 11:35:06 +0000
Received: by mail-oi0-f48.google.com with SMTP id h136so744931oig.21
for <bitcoin-development@lists.sourceforge.net>;
Wed, 30 Jul 2014 04:35:00 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.144.161 with SMTP id sn1mr4838022obb.82.1406720099952;
Wed, 30 Jul 2014 04:34:59 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Wed, 30 Jul 2014 04:34:59 -0700 (PDT)
In-Reply-To: <BCE1032B-A181-4A07-B04A-CAFFE975DE5A@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>
<CANEZrP1tn_j-bjcbokq-egVhS_x7M-L06bLb8toJeTg6oT+mcg@mail.gmail.com>
<BCE1032B-A181-4A07-B04A-CAFFE975DE5A@coinqy.com>
Date: Wed, 30 Jul 2014 13:34:59 +0200
X-Google-Sender-Auth: VukSwGonIAwhEt8NiINBg20MoUg
Message-ID: <CANEZrP3FR4woBMV-Zp84CUJjT-bZweanWTJZgy5BCJY-tO-Tzg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Mark van Cuijk <mark@coinqy.com>
Content-Type: multipart/alternative; boundary=089e0158ac78db4dc304ff678bff
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: 1XCS9x-0008GD-Rq
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: Wed, 30 Jul 2014 11:35:06 -0000
--089e0158ac78db4dc304ff678bff
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
That would definitely be a new BIP.
But firstly it'd make sense to implement it and make sure that the payment
processors intend to use it. Like I said, I wasn't very successful so far
in getting them to make useful memo fields. I'm hoping that once wallets
start actually recording and displaying the memo in their transactions list
that will change.
On Wed, Jul 30, 2014 at 9:54 AM, Mark van Cuijk <mark@coinqy.com> wrote:
> On 28 Jul 2014, at 15:32 , Mike Hearn <mike@plan99.net> wrote:
>
> > 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 ....
>
> I can probably pick up writing the proposal.
>
> However, I=E2=80=99m not sure what process to follow. Should I format the=
proposal
> as a new BIP or should it become part of BIP.70? How does the extensions
> process you=E2=80=99re working on going to describe the process?
--089e0158ac78db4dc304ff678bff
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">That would definitely be a new BIP.<div><br></div><div>But=
firstly it'd make sense to implement it and make sure that the payment=
processors intend to use it. Like I said, I wasn't very successful so =
far in getting them to make useful memo fields. I'm hoping that once wa=
llets start actually recording and displaying the memo in their transaction=
s list that will change.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
Jul 30, 2014 at 9:54 AM, Mark van Cuijk <span dir=3D"ltr"><<a href=3D"m=
ailto:mark@coinqy.com" target=3D"_blank">mark@coinqy.com</a>></span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On 28 Jul 2014, at 15:32 , M=
ike Hearn <<a href=3D"mailto:mike@plan99.net">mike@plan99.net</a>> wr=
ote:<br>
<br>
> 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 tog=
ether over at BitPay/Coinbase and get them to put useful text in the memo f=
ield instead of random numbers. Baby steps ....<br>
<br>
</div>I can probably pick up writing the proposal.<br>
<br>
However, I=E2=80=99m not sure what process to follow. Should I format the p=
roposal as a new BIP or should it become part of BIP.70? How does the exten=
sions process you=E2=80=99re working on going to describe the process?</blo=
ckquote></div>
<br></div>
--089e0158ac78db4dc304ff678bff--
|
