blob: 6f284d889d2c688eb1ac00878c1aabbe96fcaf6b (
plain)
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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@coinqy.com>) id 1XCOim-0003K0-U9
for bitcoin-development@lists.sourceforge.net;
Wed, 30 Jul 2014 07:54:48 +0000
Received: from prei.vps.van-cuijk.nl ([79.170.90.37])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1XCOil-0002W0-LA
for bitcoin-development@lists.sourceforge.net;
Wed, 30 Jul 2014 07:54:48 +0000
Received: from [192.168.29.45] (unknown [89.146.26.107])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(No client certificate requested) (Authenticated sender: mo_mark)
by prei.vps.van-cuijk.nl (Postfix) with ESMTPSA id 173E341B78;
Wed, 30 Jul 2014 09:54:40 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Mark van Cuijk <mark@coinqy.com>
In-Reply-To: <CANEZrP1tn_j-bjcbokq-egVhS_x7M-L06bLb8toJeTg6oT+mcg@mail.gmail.com>
Date: Wed, 30 Jul 2014 09:54:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Mike Hearn <mike@plan99.net>
X-Mailer: Apple Mail (2.1878.6)
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: 1XCOil-0002W0-LA
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 07:54:49 -0000
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=92m 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=92re working on going to describe the process?=
|
