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
|
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 B7EE0412
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 7 Jan 2017 20:12:31 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com
[209.85.218.53])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 096221A7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 7 Jan 2017 20:12:30 +0000 (UTC)
Received: by mail-oi0-f53.google.com with SMTP id 128so457311509oig.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 07 Jan 2017 12:12:30 -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=FHoIr3uFWnoeX87E22W4pbZymk90E7zXNCRauj7af30=;
b=eFY6ypycU9CjEbd1WwPY9gUJPIzy4dHXpOAWg5Mje10Bi5URiy6Lu724q775/61Hf6
5AxxIzPjYM8vdq55Ss5R24BZMdMWrQwjljhiBldHajzvVSzSovCnQoIqcoIpMwcqfRN1
VBsvas6FJpS44BGhk6TXK4eOrC6Z31XnjaPkBorIWS2xegNqIf97zsrLdxQkTOAXcbKK
fM+NQgv2OXJgaOh4ZeAy9PcXMgIZUusurtwxh9HlAY8OhrLaH3eoPHja7bAwjPHnNUcC
SYwbzlCMzfzbtDlDZmAWZrvIiyAVTANoOgBgFfqVXOxKWyaw687ry2tgks/Am16munzh
USdQ==
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=FHoIr3uFWnoeX87E22W4pbZymk90E7zXNCRauj7af30=;
b=e121SdRkxqoD2EGm+rzrU5CUPDbFATZWTRzX7WxmALrdp4z8YgtDWqWt9u8j5kJMeq
xjmzDVpjjwaSOnY6WjEULxrzhNLXpkdjJPJ9m9IIX0gwFPlZFsynKAF8kpYI3daQiZOs
VtJEyYf3bXFiMrp/Ri01SqPZPeEg4tEZG0pUX/ZgeG8PckZ0+FpArFliYkIhKXrE2q0N
IUNV+vDq/mxOyXNglKLVm/m04BvzUNfBvUAK3VukMJdbRSszaYJHbWonTFbsSA/9pXBI
xCGvPT/un1zS7R15r69Rwsb0dtN/Dj88nbzswJiXRijRcJRUUrDOteEAOCG065SOzB43
o+tA==
X-Gm-Message-State: AIkVDXLeIONQYPOACTinBUwA55AsxTX3qPdHdhxOWr0GWaelhbb7KOKquZhzfhdmrkNBtkv2QBn7au5tNGGASQ==
X-Received: by 10.202.242.67 with SMTP id q64mr34658188oih.98.1483819950288;
Sat, 07 Jan 2017 12:12:30 -0800 (PST)
MIME-Version: 1.0
Sender: nbvfour@gmail.com
Received: by 10.182.167.97 with HTTP; Sat, 7 Jan 2017 12:12:29 -0800 (PST)
In-Reply-To: <CABr1YTfc0BZ21-mwMohqo8_v8D1QnYiGB_SMeCLwFChY2MV_zA@mail.gmail.com>
References: <7169224.bI6Cz5OEL8@cherry>
<CABr1YTfc0BZ21-mwMohqo8_v8D1QnYiGB_SMeCLwFChY2MV_zA@mail.gmail.com>
From: Chris Priest <cp368202@ohiou.edu>
Date: Sat, 7 Jan 2017 12:12:29 -0800
X-Google-Sender-Auth: Ax14551PMSBMN-aFewUiqZJ-HKI
Message-ID: <CAAcC9ysBJcSyMoTAuyFL+1D4m=-LZOgQF_pb4AFC5vpv-yMAHQ@mail.gmail.com>
To: Eric Lombrozo <elombrozo@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
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_DNSWL_NONE,
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
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:12:31 -0000
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
>>
>
|
