blob: 3fedbe920d2c96035122ace97f1ea63fefa682b3 (
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
66
67
68
69
70
71
72
73
74
75
76
77
78
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1XeKEu-0000Uh-Pn
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Oct 2014 08:47:24 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.176 as permitted sender)
client-ip=209.85.213.176; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f176.google.com;
Received: from mail-ig0-f176.google.com ([209.85.213.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XeKEu-00026u-4y
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Oct 2014 08:47:24 +0000
Received: by mail-ig0-f176.google.com with SMTP id hn15so16960935igb.3
for <bitcoin-development@lists.sourceforge.net>;
Wed, 15 Oct 2014 01:47:18 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.147.135 with SMTP id n7mr9636009icv.25.1413362838884;
Wed, 15 Oct 2014 01:47:18 -0700 (PDT)
Received: by 10.64.141.112 with HTTP; Wed, 15 Oct 2014 01:47:18 -0700 (PDT)
Date: Wed, 15 Oct 2014 10:47:18 +0200
Message-ID: <CA+s+GJApfj5OAxGyHG9CsmRHTpAQBgC44iU2U99LwNGNZDATBw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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
(laanwj[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: 1XeKEu-00026u-4y
Subject: [Bitcoin-development] Proposed BIP status changes
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, 15 Oct 2014 08:47:24 -0000
These BIPs should go to Final state - they are implemented all over
the place, and are thus entirely fixed in place now. Any changes would
require a new BIP as amandment:
- BIP 14 (BIP Protocol Version and User Agent)
- BIP 21 (URI Scheme)
- BIP 22 (getblocktemplate - Fundamentals)
- BIP 31 (Pong Message)
- BIP 34 (Block v2, Height in coinbase)
- BIP 35 (mempool message)
- BIP 37 (Bloom filtering)
Let me know if you (don't) agree.
Wladimir
|
