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
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 78DBB305
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 28 Jun 2015 15:35:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
[209.85.212.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 820EFA7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 28 Jun 2015 15:35:19 +0000 (UTC)
Received: by wicnd19 with SMTP id nd19so79685370wic.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 28 Jun 2015 08:35:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=R356/R7I6dIcn1itb7Ev355SomuGnO81N+JP5FTbJ2U=;
b=CfcEJ0tNmHnoeJVDd0qldqCLqgavrUlzoJq0Kli3xD73jcjUylq/hCe9RhvFnvB6zr
n2rDatf8YZHAd/sxmbY+MFJJdOZt7R5WLIk5H7jYN74yTbBwT4YlFSE/NmXKs1MRaR98
QMWEq7n1ndN2VT086XtvD2o56H7ZltzGT+Nwf1o4+83vIck/q9J84R5toG0BRSQ/fUK0
PBAGPItxMLlgH1xOieizFyNT1ryqto/Gu2IunlYO3ipW1raSbyjUd4cKMhLx6sOId2b0
1qJ63plZXNXaAYlPzf/sOd5I6wBvERfW3M+GnaVDBt+AFbbCbXKkDi4GvS+1fpKgm050
Id+g==
X-Gm-Message-State: ALoCoQl9fZ2aBaDabxktThl7yTW93gUb3pswUIcRzRwektnx3fshpYG87V4nEEHQZa/3qQWJGRLg
MIME-Version: 1.0
X-Received: by 10.194.58.7 with SMTP id m7mr20256515wjq.109.1435505718068;
Sun, 28 Jun 2015 08:35:18 -0700 (PDT)
Received: by 10.194.95.168 with HTTP; Sun, 28 Jun 2015 08:35:17 -0700 (PDT)
In-Reply-To: <558FF307.9010606@bitcoins.info>
References: <COL402-EAS127289185B11D0D58E1F5E6CDAE0@phx.gbl>
<558B7352.90708@bitcoins.info>
<CABm2gDrCxLyxC=BkgiQOjRczy26kQOZb2+p9xDXOh4HuDG8nRw@mail.gmail.com>
<558D46EC.6050300@bitcoins.info>
<CABm2gDojz6PHdRKxRkMZh-gfYLdcekVfeQMz5r_4EYc-j5tn+w@mail.gmail.com>
<558E9C06.9080901@bitcoins.info>
<CABm2gDpTuEoaXZ_M166UEe+z6t-hq39yJaF3K+aL_Ra836jnSg@mail.gmail.com>
<558FF307.9010606@bitcoins.info>
Date: Sun, 28 Jun 2015 17:35:17 +0200
Message-ID: <CABm2gDpHL3RUXUK_PAiPv49EcxgjBSjPBwf=4VLhW0Y28OE=FQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Milly Bitcoin <milly@bitcoins.info>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP Process and Votes
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jun 2015 15:35:20 -0000
On Sun, Jun 28, 2015 at 3:13 PM, Milly Bitcoin <milly@bitcoins.info> wrote:
> I never said something was approved by garzik added something after it was
> opposed. What I said was a proposal was made and 4 people commented on the
> Github. He then tweeted there was near universal approval before most
> people even heard about the subject. It was not controversial but i was
> pointing out the arrogance of some of the developers. He considers the
> entire universe of Bitcoin stakeholders to be a very small group of
> insiders, not the entire universe of Bitcoin users. Another thing I have
> seen on Github for bitcoin.org is how some the maintainers change the rules
> on the fly. Sometimes they say a proposal had no objections so it is
> approved. Other times they say a proposal has no support so it is rejected.
Ok, I misunderstood.
Well, the fact is that the number of capable reviewers is quite small.
If more companies hired and trained more developers to become bitcoin
core developers that situation could change, but that's where we are
now.
> You are also trying to say that the core developers actually have little
> influence and are not "deciders" because anyone can fork the code. That has
> already been discussed at length and such an argument is faulty because
> there is a constraint that your software is incompatible with everyone else.
Only if you change the consensus rules (which are, in fact, a
relatively small part of the code).
Mike mantains Bitcoin XT and that's fine, Peter Todd maintains patches
with the replace by fee policy, libbitcoin also changes many
non-consensus things, there's code written in other languages...
There's multiple counter-examples to your claim of that argument being faulty.
Seriously, forking the project is just one click. You should try it
out like at least 9627 other people have done.
From there, you can pay your own developers (if you don't know how to
code yourself) and maybe they're also fine being insulted by you as
part of the job.
What you still can't do is unilaterally change the consensus rules of
a running p2p consensus system, because you cannot force the current
users to run any software they don't want to run.
> The issue is that there is no way right now to change the consensus rules
> except to go through the core maintainer unless you get everybody on the
> network to switch to your fork. People who keep repeating that the software
> development is "decentralized because you fork the code" without explaining
> the constraints are just cultists.
Please, stop the cultist crap. Maybe insulting people like that is how
you got people to call you a troll.
But, yes, you are right: there's no known mechanism for safely
deploying controversial changes to the consensus rules
> The discussion has nothing to do with who has the position now and I never
> said he has "control over the consensus rules." The maintainer has a very
> large influence way beyond anyone else. As for your claim that I want
> someone hurt because I am explaining the process, that is ridiculous. If
> the Core maintainers did not have significant influence to change the
> consensus rules then everybody would not be spending all this time lobbying
> them to have them changed.
Well, if you don't think he has control over the consensus rules we're
advancing.
I think that was implied from some of your previous claims. He is no
"decider" on consensus changes.
Insisting on it can indeed get him hurt, so I'm happy that you're
taking that back (or clarifying that really wasn't your position).
Influence is very relative and not only core devs have "influence".
Maybe Andreas Antonopolous has more "influence" than I have because he
is a more public figure?
Well, that's fine I think. I don't see the point in discussing who has
how much influence.
> The outside influences and stake of the developer is a relevant topic. The
> same types of things are discussed on this list all the time in the context
> of miners, users, merchants, and exchanges. Again, the developers try to
> place themselves on some kind of pedestal where they are the protectors and
> pure and everyone else (miners, users, merchants) are abusers, spammers,
> attackers, scammers, cheaters, etc. It is Garzik who voluntarily made an
> issue of how many bitcoins he holds and he made that issue in the same place
> where he announces many of the technical issues. It is very relevant that
> he has a minimal stake in Bitcoin holdings yet he goes around making major
> decisions about Bitcoin and trying to dictate who is allowed to participate
> in discussions. If a core developer has minimal stake in Bitcoin yet has
> major veto power over code change that is a problem.
Please, don't generalize. I don't think I put myself in any kind of pedestal.
That is insulting to me and many others (you may not even know and
you're insulting them).
And I think my Bitcoin holdings are completely irrelevant when judging
my contributions to the software: either they're good or not, and who
I am or how many Bitcoins I have at any given time shouldn't matter.
Again, nobody forces you to use our software, as said there's
alternatives (including forking the project right now).
> You are correct that you cannot give power to any person over the Internet
> which is why some kind of process needs to be developed that does not
> involve trying to convince one person to make the changes or a system that
> depends on unwritten, ever-changing rules maintained by a handful of people.
Well, for now the process we have is seeking consensus, and although
our definition of "uncontroversial" is very vague, I think it is quite
obvious when a proposed change is not "uncontroversial" (like in the
block size debate).
It seems to me that any other "formal process" would imply
centralization in the decision making of the consensus rules (and from
there you only have to corrupt that centralized organization to
destroy Bitcoin).
|
