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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zooko@leastauthority.com>) id 1Ug7k3-0000u3-6M
for bitcoin-development@lists.sourceforge.net;
Sat, 25 May 2013 06:14:11 +0000
X-ACL-Warn:
Received: from mail-we0-f176.google.com ([74.125.82.176])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Ug7k0-0007E1-Nb
for bitcoin-development@lists.sourceforge.net;
Sat, 25 May 2013 06:14:11 +0000
Received: by mail-we0-f176.google.com with SMTP id p58so3028052wes.21
for <bitcoin-development@lists.sourceforge.net>;
Fri, 24 May 2013 23:14:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-originating-ip:date:message-id:subject:from:to
:content-type:x-gm-message-state;
bh=OrJC+Grcm/Uf1forIAJvrYcIJDLvyw8NDmYQeoFJ180=;
b=G5kYwj+soga69uymeUaw1VoeaR0rJPv6XgjVAd9XXj8DGg0WPXczt3aGXtv8/yqf7l
M7l1VDbYlb9bL6tHAw4EXgMrvA2kqmelX8aL9TCBvhweeU1+3o8CUSCTL2RX3JS/B5mz
phANkwE/yEPf3wJhUdUUMseeQLFwo10jbW5mU5Sm7LYS5BOB3OYHL7PcYko1f2jqA9jp
WB2R20kfIzoppIgfFOz4VtSR4kuOkF5ux54Yp+cphZTZEEV8Ubwqz1v7KFvgQyuGjkyW
sK6HnMV3f6bRRb4npcZTofayFGVGqgUDVF4q/PyPkZexO63QX5YycMIiM4O+2V18Z9A1
iILA==
MIME-Version: 1.0
X-Received: by 10.194.110.169 with SMTP id ib9mr1783171wjb.12.1369460771455;
Fri, 24 May 2013 22:46:11 -0700 (PDT)
Received: by 10.194.154.135 with HTTP; Fri, 24 May 2013 22:46:11 -0700 (PDT)
X-Originating-IP: [65.101.221.166]
Date: Sat, 25 May 2013 05:46:11 +0000
Message-ID: <CAM_a8Jwo_7NJJoaKYUYo6T7U8AsDfT5=MZSXjmdYU4330OHNmw@mail.gmail.com>
From: Zooko Wilcox-OHearn <zooko@leastauthority.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQli6V4Ck95YjBToOqywCUePzzb9yiIp8fufVIuVt8ohJtCrv6sYs66m0zSTwEVQXD+aVsQZ
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: 1Ug7k0-0007E1-Nb
Subject: [Bitcoin-development] (no subject)
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: Sat, 25 May 2013 06:14:11 -0000
jgarzik wrote:
> 1) Rule changes. We don't want these.
In general? What constitutes a rule change?
For example, if I understand correctly (from what Gavin said at
Bitcoin 2013), there is a move afoot to lift the block size limit.
Although, when I went to confirm my understanding by reading the
bitcoin-development list archives, I don't see mention of this. Is
there another forum I should be reading if I want to follow Bitcoin
development?
Anyway, I hope that there are some rule changes that you would
consider for Bitcoin, although I recognize there are vast classes of
such changes that you wouldn't.
I'm trying to figure out what's the most productive way to show you,
and everyone, candidates for such changes. Things that are definitely
not suitable for merging to trunk tomorrow, but might be suitable in a
year or two, or "Next Time We Have A Hardfork".
I don't think alternative bitcoin-clones are the best venue for those.
Although they are certainly good venues for changes which can never
make it into Bitcoin.
Perhaps the best venue for such a thing is just to fork bitcoin.git on github.
Regards,
Zooko Wilcox-O'Hearn
Founder, CEO, and Customer Support Rep
https://LeastAuthority.com
|
