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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1SvwXi-0006xh-Ps
for bitcoin-development@lists.sourceforge.net;
Mon, 30 Jul 2012 20:26:18 +0000
X-ACL-Warn:
Received: from nm16-vm3.bullet.mail.ne1.yahoo.com ([98.138.91.146])
by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1SvwXh-0008FC-NM for bitcoin-development@lists.sourceforge.net;
Mon, 30 Jul 2012 20:26:18 +0000
Received: from [98.138.90.54] by nm16.bullet.mail.ne1.yahoo.com with NNFMP;
30 Jul 2012 20:26:12 -0000
Received: from [98.138.89.244] by tm7.bullet.mail.ne1.yahoo.com with NNFMP;
30 Jul 2012 20:26:12 -0000
Received: from [127.0.0.1] by omp1058.mail.ne1.yahoo.com with NNFMP;
30 Jul 2012 20:26:12 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 229862.48568.bm@omp1058.mail.ne1.yahoo.com
Received: (qmail 14949 invoked by uid 60001); 30 Jul 2012 20:26:12 -0000
X-YMail-OSG: CxmFH2YVM1m23um1PP5xgtpdiK.tgG0_39PI5el7z.W.937
LxuTqUoHx_QzM8FCcxQX8q35I6TFqDR.4VF9avwxKKSlF3v3Tjvx8HoSjmPo
6l4Lk.dReI95Oxzm5OAr_bodflKpAhtyYhu5sqn4BqveQYsmYZEthII4uljI
SC181QxtCXaQFcGvebYnZwUBhh0FGZ9uQ61aElfwG5e6v7jZg6yfunu_2Mie
hVGCOgRXZiToVaIcydYD8KsdN6kjtvtsBw_pYNruSWwv7VpyduasP89LExz6
z_orlZIlbORgQFG6RrZuE46ZWloMbkwA._PK_0awLPLFynGGwRGatlXP5KHj
5Z7CBbW54QtdaPFKAkGFw.LV0GQGha6y_tOpknwYAv20BMqLOf6g1R8gEX3Z
u6o0pyWizq6JOZJKXj5oUObKlv7sEvsdOdfRHTSOeLXZIhq71O_eY8icFJAu
xNZf1RY1lS2QR5xYTexg1i8tI5XYwcQ--
Received: from [187.57.207.48] by web121004.mail.ne1.yahoo.com via HTTP;
Mon, 30 Jul 2012 13:26:12 PDT
X-Mailer: YahooMailWebService/0.8.120.356233
Message-ID: <1343679972.9880.YahooMailNeo@web121004.mail.ne1.yahoo.com>
Date: Mon, 30 Jul 2012 13:26:12 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-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
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.91.146 listed in list.dnswl.org]
0.0 FSL_FREEMAIL_2 FSL_FREEMAIL_2
0.0 FSL_FREEMAIL_1 FSL_FREEMAIL_1
X-Headers-End: 1SvwXh-0008FC-NM
Subject: [Bitcoin-development] BIP 22 - getmemorypool
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
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, 30 Jul 2012 20:26:18 -0000
Hi,
luke-jr wants me to split this BIP into 3 separate BIPs because he says that other devs felt it was too unfocused and covered too many topics. However this discussion took place on IRC, and I never saw any of it to ascertain what happened (BIP 1 says drafts should be evaluated on the mailing list).
I think a discussion of BIP 22 perhaps did happen on the mailing list, but I don't remember it. Sorry if that's the case.
Anyway before granting the permission to allow this proposal to be pared down, and new BIPs granted for the non-core parts of this proposal, I want to know what people think. I'm not a miner myself, so I'm prescient of my lack of knowledge in the topic.
https://en.bitcoin.it/wiki/BIP_0022
Thanks
|
