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
|
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 <zgenjix@yahoo.com>) id 1S7pnc-0003mo-2B
for bitcoin-development@lists.sourceforge.net;
Wed, 14 Mar 2012 15:07:36 +0000
X-ACL-Warn:
Received: from nm40-vm4.bullet.mail.ne1.yahoo.com ([98.138.229.180])
by sog-mx-4.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1S7pna-0007rd-Um for bitcoin-development@lists.sourceforge.net;
Wed, 14 Mar 2012 15:07:36 +0000
Received: from [98.138.90.50] by nm40.bullet.mail.ne1.yahoo.com with NNFMP;
14 Mar 2012 15:07:29 -0000
Received: from [98.138.89.174] by tm3.bullet.mail.ne1.yahoo.com with NNFMP;
14 Mar 2012 15:07:29 -0000
Received: from [127.0.0.1] by omp1030.mail.ne1.yahoo.com with NNFMP;
14 Mar 2012 15:07:29 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 537552.78772.bm@omp1030.mail.ne1.yahoo.com
Received: (qmail 88018 invoked by uid 60001); 14 Mar 2012 15:07:29 -0000
X-YMail-OSG: 1XA9ZXEVM1l0fVfJiJvxaUp41mRNqTVtjuEOn7ajjCkC6Tq
yW28Pg4qYeT6EiLvUAI7TQZCNy7W4Iq0MzjG5uTaczm845whSIPaPUwRHpcU
.5Y53naY86wtetoJt5Tq9eA65cbxPteE714I5kcGLU9kuAbaHsICvE4VE4Eo
sGTIRwOkAgKKqoK63SDcbnMMibxLUQcVPMfmcbG2l49i7FneglKDqmIBIG0k
IJM9bVtNU0rTNyFV5OWVw1N0CMb2mZCVWmfCyroXqSCOervpBqhHNCAKgct5
aXtfLzQ4B1VqiCTJ3qPyLQUNFdgcFPyHjdqAJkAjSX3pGM1vsF8l0igj6ZcA
v_0_ni9Qy0Q_nFc8Rh9DIoOed3FAufdgVojYhktv7bhs1BkPINZOj..rvc.V
v9zCcO9eWSZbZNyF8H4dMZ0K7WPVJnatHhAFXHU6P7hoS2fTxyPiA94VDl3N
1oLEQcewWiEHFO.6NzpfN9_VVrRk61j2qssSh3zB7ZrhW5VenEpm5o.OC394
NkX60Pfg-
Received: from [92.20.175.107] by web121006.mail.ne1.yahoo.com via HTTP;
Wed, 14 Mar 2012 08:07:29 PDT
X-Mailer: YahooMailWebService/0.8.117.340979
Message-ID: <1331737649.82143.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Date: Wed, 14 Mar 2012 08:07:29 -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=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.4 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.229.180 listed in list.dnswl.org]
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.5 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1S7pna-0007rd-Um
Subject: [Bitcoin-development] BIP 18 (or not?)
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: Wed, 14 Mar 2012 15:07:36 -0000
Hi,=0A=0Aluke-jr withdrew BIP 16 and put forwards support for BIP 17. So no=
w there's a consensus to move forwards.=0A=0AHowever he submitted BIP 18 to=
me today. From looking it over, I'm not even sure the idea is tenable nor =
see the purpose when we are adopting BIP 17. Personally I'd rather not see =
a high turnover in protocol design when something works (now that we have v=
iable multisig transactions) even compromising on the position of a perfect=
design.=0A=0Ahttps://en.bitcoin.it/wiki/BIP_0018=0A=0AUsually for a BIP, s=
omeone submits it to me, I review to see whether the idea is technically so=
und (not making judgements on the validity), the community discusses the id=
ea and I evaluate the support at the end to change the status. In general I=
try to accept all BIPs in the interests of fairness, rather than holding a=
vote or being the executioner.=0A=0A"Once the champion has asked the Bitco=
in community as to whether an idea has any chance of acceptance, a draft BI=
P should be presented to=A0bitcoin-development@lists.sourceforge.net. This =
gives the author a chance to flesh out the draft BIP to make properly forma=
tted, of high quality, and to address initial concerns about the proposal.=
=0AFollowing a discussion, the proposal should be sent to the Bitcoin-dev l=
ist with the draft BIP and the BIP editors <BIPs@Bitcoin.org>. This draft m=
ust be written in BIP style as described below, else it will be sent back w=
ithout further regard until proper formatting rules are followed."=0A=0AI d=
on't think BIP 18 has followed this discussion before being accepted. Neith=
er have many other BIPs as we're a small community, and so far we avoided t=
his unneeded level of bureaucracy. However I think this is a good thing to =
do here.=0A=0AShould BIP 18 be accepted into the repo or not?=0A=0A"The BIP=
editor will not unreasonably deny a BIP. Reasons for denying BIP status in=
clude duplication of effort, being technically unsound, not providing prope=
r motivation or addressing backwards compatibility, or not in keeping with =
the Bitcoin philosophy."=0A=0A"For a BIP to be accepted it must meet certai=
n minimum criteria. It must be a clear and complete description of the prop=
osed enhancement. The enhancement must represent a net improvement. The pro=
posed implementation, if applicable, must be solid and must not complicate =
the protocol unduly."=0A=0A(quotes from BIP 1)
|
