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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1Z521n-0003qG-LC
for bitcoin-development@lists.sourceforge.net;
Wed, 17 Jun 2015 01:20:31 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.179 as permitted sender)
client-ip=209.85.213.179; envelope-from=gmaxwell@gmail.com;
helo=mail-ig0-f179.google.com;
Received: from mail-ig0-f179.google.com ([209.85.213.179])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z521n-0008Bp-0k
for bitcoin-development@lists.sourceforge.net;
Wed, 17 Jun 2015 01:20:31 +0000
Received: by igbos3 with SMTP id os3so57480596igb.0
for <bitcoin-development@lists.sourceforge.net>;
Tue, 16 Jun 2015 18:20:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.7.68 with SMTP id h4mr7259748iga.40.1434504025788; Tue,
16 Jun 2015 18:20:25 -0700 (PDT)
Received: by 10.107.147.213 with HTTP; Tue, 16 Jun 2015 18:20:25 -0700 (PDT)
In-Reply-To: <CAOG=w-s5D2eaF0biPEEeFgLKLNpA3ho1Sk4mCPQNpVOeNBgr-A@mail.gmail.com>
References: <CAOG=w-uufDPkQSEi1K_L82j4OXObGmESnfYyxi1z99fcBCotcg@mail.gmail.com>
<CAOG=w-s5D2eaF0biPEEeFgLKLNpA3ho1Sk4mCPQNpVOeNBgr-A@mail.gmail.com>
Date: Wed, 17 Jun 2015 01:20:25 +0000
Message-ID: <CAAS2fgSj3=Pzo0emtdBBdYxny7BDf1ENzHxY+Ahm0Eiry9dDGw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mark Friedenbach <mark@friedenbach.org>
Content-Type: text/plain; charset=UTF-8
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-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: 1Z521n-0008Bp-0k
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [BIP draft] Consensus-enforced
transaction replacement signalled via sequence numbers
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, 17 Jun 2015 01:20:31 -0000
On Wed, Jun 17, 2015 at 1:00 AM, Mark Friedenbach <mark@friedenbach.org> wrote:
> Given that we have had more than two weeks of public discussion, code is
> available and reviewed, and several community identified issues resolved, I
> would like to formally request a BIP number be assigned for this work. Will
> the BIP editor be so kind as to do so to allow the BIP consensus process to
> proceed?
BIP 68, unless you have objections.
|
