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
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
|
Return-Path: <nbvfour@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 93BD78A1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 7 Jan 2017 20:26:33 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com
[209.85.218.52])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A4F14127
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 7 Jan 2017 20:26:31 +0000 (UTC)
Received: by mail-oi0-f52.google.com with SMTP id b126so652467755oia.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 07 Jan 2017 12:26:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:sender:in-reply-to:references:from:date:message-id
:subject:to:cc;
bh=4OoHXUc1T+k9tnqfiSEK3qAMUnpnRB+huNP6jkX9mjM=;
b=SLfkaTkV7qZSIC4QU2b/LVZJUYC3ahjxNlhzXMHMxh3N8Ax3Tg10YrCyShMkIHHLO+
my9zpwCLgZ7/MH0ixysSl4dkzoXLJhVoFIHKyhVj3n2g2IKi7hbAGxC8+4qwVKttQO9m
NdfTBkNtL9SiDwQNRjAk+FHSLzw+66DHMrWxYJsdxL6A/HW5iEKd6AQ26XtvU68B+g83
qv0LS5CN91gMXVp6Nj1JX80GW9yIKk/3XZFIWmDDfotqDqbYI+e2YSh6UCEuQ85Jax2U
VU3AxhbVIUE/UBASszcVesP+PB98xih54j1sEKUKm5HwbqoUEycL0wvHXrWsbTqYQvPD
/RAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to:cc;
bh=4OoHXUc1T+k9tnqfiSEK3qAMUnpnRB+huNP6jkX9mjM=;
b=OZlHNW5YbbaANs/adhOOysqhDrJEkK9++71ja0RZ2BeIueyyevNib9GXR0Yc18Lc2H
DM+KwidOk4EWvX7lHANR6vZTuP3tBl5Z4XjxvQwO9DUADRqq3zO3m8hiRhMvtrbdC1Ib
f2t8NpP6LrOaBpn2OxidHkqUfbZcza4yWsk1wOynrRz+nTRuxLA0seZ14njJ6iF+Yk/m
N7cVBilcU+ze/xovkoeecUDQuUqM97VMFEe/whrQ6ivdrEnvgvwDYSDmOMoqD1UbO2iU
164AWXm5jf2S2ONZMXZJpyTVqDiH2MhEYMlgaus5+sEwHxXJDR2oLE4r8wdAYpRmuVIX
rIDg==
X-Gm-Message-State: AIkVDXIrgUKHWplheU3jmGw8kZf1elXhrogHaQyY/EoaFQwl1S+YHhR1fcm+l7nI3Lldy6GODiJBQCa6gfBNVw==
X-Received: by 10.202.242.67 with SMTP id q64mr34673382oih.98.1483820790926;
Sat, 07 Jan 2017 12:26:30 -0800 (PST)
MIME-Version: 1.0
Sender: nbvfour@gmail.com
Received: by 10.182.167.97 with HTTP; Sat, 7 Jan 2017 12:26:30 -0800 (PST)
In-Reply-To: <CAFVRnyqw2w1rHN=ShLBsadB3henEM9BZxxdXj+4QY6NQAyZ4Fg@mail.gmail.com>
References: <7169224.bI6Cz5OEL8@cherry>
<CABr1YTfc0BZ21-mwMohqo8_v8D1QnYiGB_SMeCLwFChY2MV_zA@mail.gmail.com>
<CAAcC9ysBJcSyMoTAuyFL+1D4m=-LZOgQF_pb4AFC5vpv-yMAHQ@mail.gmail.com>
<CAFVRnyqw2w1rHN=ShLBsadB3henEM9BZxxdXj+4QY6NQAyZ4Fg@mail.gmail.com>
From: Chris Priest <cp368202@ohiou.edu>
Date: Sat, 7 Jan 2017 12:26:30 -0800
X-Google-Sender-Auth: S9p457C6bqkpfnxLDrcJpODQzic
Message-ID: <CAAcC9ysNPC1nHumY4giCi7ffVRviNZBNfoLdS0UsghSX8NRcmw@mail.gmail.com>
To: David Vorick <david.vorick@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, FREEMAIL_FROM, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Classic 1.2.0 released
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Sat, 07 Jan 2017 20:26:33 -0000
Bitcoin Classic only changes the block format (by changing the rule
that they have to be 1MB or less). Miners are the only ones who make
blocks, so they are the only ones who mater when it comes to changing
block rules. Nodes, wallets and other software are not affected by
changing block rules. Unlike segwit, where *everybody* has to write
code to support the new transaction format.
Also, it doesn't matter that 75% of hashpower is made up of a dozen
people. That's how the system works, it's not a matter of opinion. If
you are just a node or just a wallet, and you want your voice to
matter, then you need to get a hold of some hashpower.
On 1/7/17, David Vorick <david.vorick@gmail.com> wrote:
> No, Bitcoin classic only activates if 75% of the _miners_ adopt it. That
> says nothing about the broader network and indeed is much easier to achieve
> through politicking, bribery, coercion, and other tomfoolery as 75% of the
> hashrate is ultimately only a dozen people or so.
>
> You have plenty of channels through which you can make your announcements,
> this particular one is not okay.
>
> On Jan 7, 2017 3:12 PM, "Chris Priest via bitcoin-dev" <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Bitcoin Classic only activates if 75% of the network adopts it. That
>> is not irresponsible or dangerous. It would only be dangerous if it
>> activates at 50%, because that would create a situation where its not
>> clear which side of the fork has the most proof of work.
>>
>> On 1/7/17, Eric Lombrozo via bitcoin-dev
>> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> > Your release announcement does not make it clear that Bitcoin Classic
>> > is
>> > incompatible with the current Bitcoin network and its consensus rules.
>> > It
>> > is a hard fork on mainnet with no safe activation as well as including
>> > other unsafe changes. There is also no BIP for the hard fork. There is
>> also
>> > no evidence of community wide consensus for such a hard fork. This is
>> > dangerous and irresponsible.
>> >
>> >
>> > It's wrong to announce software without correctly informing people
>> > about
>> > the contents or risks. Furthermore, there are no release notes in
>> > https://github.com/bitcoinclassic/bitcoinclassic/tree/v1.2.0/doc nor
>> > changelog. Without those, it is almost impossible for average users to
>> know
>> > what is under the hood or what has changed and time consuming for
>> > developers to assess.
>> >
>> > On Fri, Jan 6, 2017 at 2:16 AM, Tom Zander via bitcoin-dev <
>> > bitcoin-dev@lists.linuxfoundation.org> wrote:
>> >
>> >> Bitcoin Classic version 1.2.0 is now available from;
>> >>
>> >> <https://bitcoinclassic.com/gettingstarted.html>
>> >>
>> >> This is a new major version release, including new features, various
>> >> bugfixes and performance improvements.
>> >>
>> >> This release marks a change in strategy for Bitcoin Classic, moving
>> >> from
>> >> the
>> >> very conservative block size proposal based on compromise to one where
>> >> Classic truly innovates and provides a long term solution for the
>> >> market
>> >> to
>> >> choose and leave behind the restrictions of the old.
>> >>
>> >> The most visible change in this version is the decentralised block
>> >> size
>> >> solution where node operators decide on the maximum size.
>> >>
>> >> Bitcoin Classic is focused on providing users a way to get onto the
>> >> Bitcoin
>> >> network using a high quality validating node for a large set of use
>> >> cases.
>> >> Classic presents top notch quality processes in this release, to help
>> >> anyone
>> >> running Bitcoin.
>> >>
>> >> We include in this release various projects with the beta label.
>> >> People
>> >> who
>> >> want to use the Classic node as an on-ramp to Bitcoin will find them
>> >> interesting. These projects will need to be enabled in the config by
>> >> those
>> >> that want to test them.
>> >>
>> >> More background information on this release and Classic can be seen in
>> >> this
>> >> video: https://vimeo.com/192789752
>> >> The full release notes are on github at
>> >> https://github.com/bitcoinclassic/bitcoinclassic/releases/tag/v1.2.0
>> >>
>> >> --
>> >> Tom Zander
>> >> Blog: https://zander.github.io
>> >> Vlog: https://vimeo.com/channels/tomscryptochannel
>> >> _______________________________________________
>> >> bitcoin-dev mailing list
>> >> bitcoin-dev@lists.linuxfoundation.org
>> >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>> >>
>> >
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
|
